⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Observability & Monitoring Interview Questions Scenario 57 of 116 in Observability & Monitoring
Staff SRE / Principal Architect [L3] Observability OpenTelemetry & Tracing Staff SRE Scenario [L3]
🎯 Target Role / Context: Observability Scenario #56 (L3) · Procedure #1: Clear Deadlock

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, while the other expects B3 headers such as X-B3-TraceId.

#Observability #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
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? The Linux Foundation's Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "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."

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.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability Distributed traces High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
  2. Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability Distributed traces Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
  3. Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability Distributed traces Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
  4. Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability Distributed traces Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.
Advertisement
Want more Observability & Monitoring scenarios?
Explore our complete collection of scenario-based Observability & Monitoring interview runbooks.
Browse All Observability & Monitoring Questions →