tsuga-debug-missing-trace-propagation

What problem does it solve?

This Skill helps you diagnose why distributed traces fail to connect across services, resulting in missing parent/child span relationships, orphaned spans, or multiple unrelated trace IDs for the same request.

Core Features & Use Cases

• Trace parenting diagnosis: Determines whether callee spans are missing parentSpanId, have a wrong trace, or correctly link back to caller spans.
• Propagation boundary checks: Validates whether HTTP/gRPC/messaging boundaries correctly inject and extract trace context (including transport-specific interceptor and header/attribute handling).
• Root-cause oriented remediation guidance: Recommends the minimal code/config change for the identified language and transport and provides a verification loop using Tsuga span searches.
• Use Case: When a request enters Service A and triggers Service B via HTTP/gRPC/queues, but Service B’s spans appear unlinked, this Skill guides you through finding the missing propagation point and correcting it.

Quick Start

Use this skill to investigate a suspected trace propagation break between a caller and callee service by specifying both service names, the transport type, and the languages of the caller and callee.