OpenTracing and Containers: Depth, Breadth, and the Future of Tracing
summary
OpenTracing provides a vendor-neutral API that decouples instrumentation from backend analysis and demonstrates working integrations with Zipkin and LightStep; a live DonutSalon demo shows the fryer consuming ~60–69% of request time and baggage tags identifying “cinnamon” as the culprit so a lock is found. It argues Kubernetes plus an L7 proxy (Envoy/linkerd) can give zero-touch, black-box spans by extract/inject context propagation, and the demo traces validate that approach end-to-end.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:56What is Tracing
- 6:45History of Tracing
- 12:13Donut Salon Demo
- 19:08Future of Tracing
- 24:16Thank you
- 26:27AppDash
- 27:26Open Contributions
- 27:58Log4J vs OpenTracing
- 29:42What is OpenTracing
- 30:39The Real Value
- 31:29Saving Money
- 32:10Conclusion
related talks
19mKeynote: OpenTracing and Containers: Depth, Breadth, and the Future of Tracing - Ben Sigelman
38mOpenTracing Project Intro
23mIntroduction to OpenTracing
36mOpenTracing Project Deep Dive
16mPragmatic execution tracing
24mDistributed Tracing : New DevOps Foundation.
14mLeveraging Distributed Tracing in Kubernetes & Containerized Environments
46mVisualising and tracing requests through a cluster: Intergrating OpenTracing into OpenStack Swift
