Q: Distributed traces are broken between two services after one team migrated from B3 headers to W3C Trace Context. What is happening and how do you fix it?
The services are using different propagation formats. One service injects trace context using headers such as traceparent and tracestate,...
#Observability #Procedure #1: Clear Deadlock #L3 #Monitoring #Prometheus #SRE
🎙️ Candidate Opening & Architectural Context
""Logs tell you what happened, metrics tell you where to look, and distributed traces pinpoint the exact slow component. The interviewer is testing: Trace propagation standards and cross-team compatibility.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Initial Diagnostics & Root Cause Analysis
The services are using different propagation formats. One service injects trace context using headers such as traceparent and tracestate, while the other expects B3 headers such as X-B3-TraceId. The downstream service starts a new trace because it cannot extract the parent context.
- Configure all services to use one standard, preferably W3C Trace Context for new systems.
- During migration, enable multi-propagator support so services can extract both B3 and W3C while injecting the chosen standard.
- Verify API gateways, service meshes, and async message producers preserve trace headers.
2️⃣
Remediation & Permanent Safeguards
To fix it: Trace propagation is a contract. It must be standardized the same way API auth headers are standardized.
- Add a test that sends a request through both services and asserts one shared trace ID.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Configure all services to use one standard, preferably W3C Trace Context for new systems.."
⚡ 60-Second Elevator Pitch Talking Points
- Configure all services to use one standard, preferably W3C Trace Context for new systems.
- During migration, enable multi-propagator support so services can extract both B3 and W3C while i...
- Verify API gateways, service meshes, and async message producers preserve trace headers.
Advertisement