Confirm that all services in the call chain use a propagator that supports W3C TraceContext (traceparent and tracestate headers)
Register the W3C TraceContext and W3C Baggage propagators in the OTel SDK global propagator configuration at application startup
Verify that HTTP client instrumentation in each service reads incoming context and injects outgoing headers automatically
Use Baggage to carry per-request metadata such as tenant ID or feature flags across service boundaries without adding span attributes in every service
Test end-to-end propagation by tracing a synthetic request and confirming all downstream spans share the root trace ID
Known gotchas
Baggage is propagated across all downstream services and can leak sensitive data if used carelessly; treat Baggage values as potentially visible to all services in the call graph
Some frameworks and HTTP clients strip unknown headers by default; ensure traceparent and baggage are in the allowlist if header filtering is applied at any hop
Mixing propagation formats (e.g., B3 on some services, W3C on others) breaks context propagation at the boundary; standardize on one format across the entire system or use a multi-format propagator
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp