OpenTracing Isn't Just Tracing: Measure Twice, Instrument Once
summary
OpenTracing provides a vendor-neutral API that turns per-service instrumentation into structured spans, baggage and tags that can feed logging, metrics and tracing. Demo wires the sample drone Utz app into LightStep and Prometheus, showing a buy-donuts request taking six and a half seconds and isolating a slow gRPC check call. Code to convert spans into Prometheus latency and error metrics is small, and the ecosystem needs language multiplexers and library plugins to reach turnkey tracing.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:11Why Care About Tracing
- 1:20Why Arent We Already Doing This
- 3:04What is OpenTracing
- 4:52OpenTracing is relatively new
- 7:21What can you use it for
- 9:15The Venn Diagram
- 9:37Turnkey Tracing
- 12:05Drone Utz Demo
- 13:12LightStep Demo
- 16:19Join Us
- 18:54Distributed Tracing Salon
- 19:27Questions
related talks
23mIntroduction to OpenTracing
38mOpenTracing Project Intro
36mOpenTracing Project Deep Dive
19mKeynote: OpenTracing and Containers: Depth, Breadth, and the Future of Tracing - Ben Sigelman
16mPragmatic execution tracing
59mOpenTelemetry will save your day and night
32mDistributed Tracing in Action: Our Journey with OpenTelemetry
22mOpen Telemetry for API Monitoring