Keynote: OpenTracing and Containers: Depth, Breadth, and the Future of Tracing - Ben Sigelman
summary
OpenTracing defines a vendor-neutral API for distributed tracing and shows how zero-touch black-box instrumentation can be achieved with local proxies or daemonsets in Kubernetes, using extract/inject to propagate context. A live demo of DonutSalon exposes a concurrency bottleneck at the fryer with a 141 pending lock wait and P99.9 traces up to 1.2 minutes; baggage carries a client ID so requests are traceable across services. OpenTracing binds to Zipkin, Jaeger or LightStep, scales to millions of spans per second, and enables tracing without heavy app changes.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:33Why Tracing
- 3:09OpenTracing
- 6:10Tracing History
- 7:38Donut Salon
- 13:39Vendor Neutrality
- 14:29Kubernetes
related talks
33mOpenTracing and Containers: Depth, Breadth, and the Future of Tracing
07mKeynote: OpenTracing Project Update
23mIntroduction to OpenTracing
38mOpenTracing Project Intro
26mOpenTracing Isn't Just Tracing: Measure Twice, Instrument Once
36mOpenTracing Project Deep Dive
24mDistributed Tracing : New DevOps Foundation.
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
