OpenTracing Project Intro
summary
OpenTracing presents a narrow instrumentation API that aims to eliminate vendor lock-in by letting code propagate a small span context blob and then bind once per process to any backend like Jaeger Zipkin or LightStep. It reports concrete adoption: support in 100+ open source packages and formal libraries in about nine languages, works inside Couchbase CockroachDB and Envoy, and focuses on making instrumentation easy while leaving storage, UI and sampling policies to downstream tracers.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:01Microservices: 1 story, N storytellers
- 3:42Systems are not just distributed, they're Concurrent
- 9:35Great... So why isn't tracing ubiquitous?
- 13:55Where does tracing code live?
- 16:27Tracing: the Mental Model
- 19:43OpenTracing architecture
- 21:25A young, fast-growing project 2 years old!
- 22:24100s of projects, 10s of tracers, 9 languages
- 24:21Getting Started with OpenTracing
- 36:18Example Request with Trace Visualization
related talks
23mIntroduction to OpenTracing
26mOpenTracing Isn't Just Tracing: Measure Twice, Instrument Once
33mOpenTracing and Containers: Depth, Breadth, and the Future of Tracing
19mKeynote: OpenTracing and Containers: Depth, Breadth, and the Future of Tracing - Ben Sigelman
34mOpenTelemetry: Overview & Backwards Compatibility of OpenTracing + OpenCensus
48mOpenTelemetry: Backwards Compatibility with OpenTracing and OpenCensus
16mPragmatic execution tracing
07mKeynote: OpenTracing Project Update