Unpacking Your OTel Baggage
summary
Claims that OpenTelemetry baggage can carry domain keys across services and that Skyscanner uses it to drive per-request QoS decisions via an injected source header. Built a language-agnostic developer API (M shell), a custom propagator to block export, automatic header injection into the mesh, and a YAML-driven Istio decision set. Runs across four regions, 24 clusters, 600 services and ~35,000 pods serving 60M RPM, removes need for global counters or no Redis, and successfully enforces priority routing while falling back to global defaults.
AI-written summary · about
chapters (9)
- 0:00OpenTelemetry Baggage intro
- 2:29Custom context propagation challenges
- 5:16What Baggage is and how it works
- 7:21What Baggage is not and limits
- 9:06Skyscanner’s Baggage use
- 11:56Improving service quality with Baggage
- 15:51Smart routing with Baggage in Istio
- 17:14Baggage best practices
- 17:56Q&A
related talks
19mInstrumenting Go Apps With OpenTelemetry
24mOTel-y Oops: Learning From Our Observability Blunders
23mOpenTelemetry Auto Instrumentation for Effortless Observability
45mSimplifying Instrumentation in complex systems at scale with Open Telemetry
24mUnlocking Advanced Processing Capabilities with OpenTelemetry
46mThe State of OpenTelemetry
08mLightning Talk: Kick-Start Distributed Tracing in Istio with OpenTelemetry
34mPanel: OpenTelemetry: Bridging Platform and Enablement