Tracing Go
summary
Claims that distributed tracing plus event collection makes latency root cause analysis practical, and describes an instrumentation library that exports spans to Google Cloud Trace, Zipkin and Jaeger, hooks the standard library HTTP trace and the Go execution tracer, and surfaces an in-process dashboard for missing exports. Shows how traces map spans to source code and on‑call owners, explains sampling costs and identifier propagation pain points, and argues critical‑path visibility (CPD) changes diagnosis from guesswork to evidence.
AI-written summary · about
chapters (9)
- 0:00Start
- 9:18Unified Build Tool
- 10:22Critical Path
- 11:59Emerging Technologies
- 13:11A Distributed Trace
- 18:49Process Diagnostics
- 19:38Everyday Challenges
- 20:51Upcoming Proposal to W3c
- 21:14Network Stacks
related talks
30mMastering Distributed Tracing with Go
22mDistributed Tracing
37mObservability, Distributed Tracing & the Complex World
16mPragmatic execution tracing
39mEfficient Debugging and Logging with OpenTelemetry in Go
40mInstrumenting GO Applications
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
34mReduce Complexity with Distributing Tracing