tsuga-debug-missing-trace-propagation

Missing trace propagation causes parent/child span relationships to break across service boundaries, resulting in multiple trace IDs for a single request. This Skill diagnoses extraction or injection failures across HTTP, gRPC, and messaging transports to identify where context linking fails.

Fixing null parent span IDs requires validating trace context propagation at the transport boundary. This Skill checks whether your caller and callee languages correctly inject and extract trace context via transport-specific interceptors and headers to restore span parenting.

Yes, the trace propagation diagnosis supports HTTP, gRPC, and asynchronous messaging scenarios. It applies transport-specific interceptor and header checks to ensure trace context is correctly propagated and linked across caller and callee services regardless of protocol.

You verify distributed trace span linking by running a Tsuga span search to confirm parent/child relationships are established. This Skill provides a verification loop to ensure the caller and callee spans correctly connect under a single trace ID after applying the recommended code fixes.

To diagnose a broken distributed trace across microservices, you need the caller and callee service names, the transport type connecting them, and the programming languages of both services. This information drives the transport-specific and language-specific propagation fix guidance provided by the Skill.