Developing Observable Applications for Production
summary
How to make production applications observable by instrumenting code to gather concrete data for debugging and performance analysis. Covers the three pillars of observability, where to place observation points, which visualizations to prioritize, and the tools available to support instrumentation and analysis.
AI-written summary · about
chapters (24)
- 0:00Introduction by Pierre Zemb
- 2:07Introduction to the topic
- 7:08The benefits of open source
- 10:29The software doesn’t stop there
- 14:10Finding the butterfly that caused the tornado
- 17:40Debugging
- 18:50The 3 steps of debugging
- 20:03The developer’s responsibility
- 21:37What can I do?
- 21:52What are the first questions an on-call person asks?
- 22:20What are on-call methods?
- 23:26What are monitoring methods?
- 24:37The 4 elements to watch
- 26:00The 4 elements to measure
- 26:57How to instrument?
- 28:46Logs
- 30:36Metrics
- 31:42Tracing
- 33:42OpenTelemetry
- 35:25Visualization
- 37:47Example of saturation
- 39:33Graphical representation of CPU time
- 41:18Lazy graph
- 44:47Acknowledgments
related talks
44mObservability: Superpowers for Developers
58mObserving Applications in Production
30mA Well-Maintained Production Application
29mObservability for Developers: How to Get From Here to There
16mUsing Observability to improve the Developer Experience
48mAPI Observability by Design: Building Systems That Tell Their Own Stories
33mWhat Developers Should Know About Observability
31mObservability for Developers: How to Get There
