Introduction to OpenTracing
summary
OpenTracing defines a vendor-neutral API for instrumenting services (Java, Go, Python and more) that manages spans, tags and inter-process propagation; it shows a concrete span parent-child model with start/finish timestamps and searchable operation names. Demo uses a microdonut app and Jaeger UI to display per-request traces, durations, tags and service call chains. OpenTracing relies on library instrumentation, supports multiple backends (Jaeger, Zipkin, LightStep), notes W3C trace-context work, and warns that sampling and buffering mean traces can be dropped.
AI-written summary · about
chapters (8)
- 0:00Introduction to OpenTracing
- 1:04Monitoring and distributed tracing
- 3:35OpenTracing architecture model
- 8:13OpenTracing components
- 12:02Tracing API and spans
- 15:01Live tracing demo with Jaeger
- 18:36Summary and resources
- 19:25Q&A on trace reliability
related talks
38mOpenTracing Project Intro
36mOpenTracing Project Deep Dive
26mOpenTracing Isn't Just Tracing: Measure Twice, Instrument Once
19mKeynote: OpenTracing and Containers: Depth, Breadth, and the Future of Tracing - Ben Sigelman
33mOpenTracing and Containers: Depth, Breadth, and the Future of Tracing
43mPractical Introduction to OpenTelemetry Tracing
16mPragmatic execution tracing
40mPractical introduction to OpenTelemetry tracing