Distributed Tracing
summary
Distributed tracing reconstructs a single request’s timeline across services by emitting spans with start/end times and parent/span IDs so you can find latency hotspots. Demo uses Go services (item + order), Redis for storage and a Jaeger backend, producing 15 spans for one flow and successfully visualizing where time is spent. Recommendations: use OpenTelemetry or OpenTracing APIs to avoid vendor lock‑in, pass context and finish spans, instrument critical paths only to limit overhead.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:50History
- 6:52Performance Analysis
- 10:47Why isnt everyone using it
- 12:13Open Tracing Standard
- 14:31Demo
- 15:10Application
related talks
49mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
42mDistributed Tracing Opening the Door to Visualisation and Correlation
34mReduce Complexity with Distributing Tracing
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
25mTracing Go
23mIntroduction to OpenTracing
16mDistributed Tracing is Awesome, Testing is Not... Until Now
30mMastering Distributed Tracing with Go