Distributed Tracing in Large Software Systems
summary
Introduces Distributed Tracing as a tool to observe operations, service calls, and performance in large, multi-team software systems. Describes what Distributed Tracing is, how it was implemented in the presenters’ systems, and gives practical recommendations and pitfalls to watch for when adopting it.
AI-written summary · about
chapters (15)
- 0:00Distributed tracing intro
- 3:17Debugging distributed systems
- 5:50Payroll page timeout
- 6:11Search ranking optimization
- 7:39OpenTelemetry spans & attributes
- 10:51Tracing HTTP requests
- 13:04Tracing messaging systems
- 15:14Simplifying tracing for teams
- 17:00Storing traces sampling
- 19:08Sampling strategies
- 21:16Choosing tracing backend
- 23:02Visualizing traces in Tempo
- 25:51Tempo search issues
- 27:32Conclusion & advice
- 28:58Q&A
related talks
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
38mDistributed Tracing: Practices, Patterns & Technologies for Debugging Microservices
28mTracing the Journey into Distributed Tracing
49mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
59mAn introduction to distributed tracing
11mKeynote: Distributed Tracing - The Struggle is Real
48mFrom Logs to Traces
29mIntroduction to Distributed Tracing
