Missing Traceparent Propagation
Use when services appear as separate traces or child spans are missing because trace context was not forwarded.
Linked toolsok
Commandsok
TraceBrowserOpsAgentUIMonitor
Symptoms
- Multiple trace IDs for one user workflow.
- Target service spans are present but disconnected.
- Propagation summary is degraded.
Likely Causes
- Outbound client did not forward traceparent.
- Proxy stripped trace headers.
- Service used local trace IDs instead of W3C context.
Checks
- Validate traceparent with /api/mcp validate_trace_context.
- Check X-PlatPhorm-Source-Site and X-PlatPhorm-Target-Site.
- Open /api/v1/network/propagation.
Evidence To Collect
- request ID
- traceparent
- tracestate
- source service
- target service
platphormctl Commands
platphormctl trace propagate --service agentui platphormctl harness run trace-propagation-check --dry-run