The path to understanding and debugging distributed systems
summary
Covers techniques for making microservice-based distributed systems observable and debuggable by developers operating in a DevOps model. Discusses observability, monitoring, APM (Application Performance Management), and structured logging, and gives concrete code examples and instrumentation patterns to help trace failing requests and diagnose production problems.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:30Mindset shift in development
- 3:38Key principles for distributed systems
- 7:12Production problem classification
- 9:19Structured contextual logs
- 12:57Log naming and levels
- 15:02Production visibility tools
- 20:07Monitoring: utility and limits
- 23:18Alerts and priorities
- 27:15Health checks and service autonomy
- 29:20APM and distributed traces
- 33:14APM instrumentation costs
- 35:21Tools by needs
- 37:51Future: observability and integrated tools
- 38:53Production testing and service quality
related talks
38mDistributed Tracing: Practices, Patterns & Technologies for Debugging Microservices
40mObservability in a Microservice World
01h 07m"Adding Observability to Distributed Systems"
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
28mOperational visibility in distributed systems
16mThe State of Observability
33mEffective observability in microservice architectures
50mZen State, and Observability of Your Inner Microservice