Observability for Developers: How to Get From Here to There
summary
Argues that observability benefits developers more than operators and shows how teams move from grepping logs to structured traces with concrete wins: a ranked-endpoint spreadsheet that prioritizes rewrites, a Geckoboard uptime chart that reveals how bad crashes are, and a feature-flagged canary rolled to a tiny percent that proves a DB index change improves user experience. Practical steps include start at the edge, instrument one endpoint, make logs machine readable, and emit correlated contextual records so fixes actually work and justify more investment.
AI-written summary · about
chapters (8)
- 0:00Observability matters
- 3:48Dev versus ops blurred
- 7:58Real-world observability stories
- 13:41Production as new language
- 16:57Instrument where you control
- 20:30Effective instrumentation tactics
- 22:36Production tools for devs
- 27:13Closing dev-ops gap
related talks
31mObservability for Developers: How to Get There
44mObservability: Superpowers for Developers
34mObservability Concepts Every Developer Should Know
13mObservability that matters
41mA peek into observability from testers lens
33mWhat Developers Should Know About Observability
44mObservability for Emerging Infra: What Got You Here Won’t Get You There
32mEssential Software Observability for Every Role: Look No Further