Observability driven development
summary
Clear claim: add observability from day one so production bugs are debuggable. Concrete tools and practices: instrument a Flask todo app with new relic, emit structured logs with request id traceability and extras instead of interpolated text, use proper log levels, and prefer OpenTelemetry for vendor portability. Real numbers and fixes: a bulk update removes N per-item selects/updates, making an async log handler and a bulk save converts a 50-update hotspot into a fast path; one case processes 8 million messages a day and gains an 8× speedup.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:47About Bianca
- 1:54What do you like
- 2:38Why develop software
- 5:28Outline
- 5:51Logging tools
- 6:53OpenTelemetry
- 7:46New Relic
- 13:49Logging
- 19:22Application
- 25:54Performance
related talks
29mObservability for Developers: How to Get From Here to There
31mObservability for Developers: How to Get There
37mObservability-Driven Development
49mObservability in Practice: How to Become Proactive with Bugs
44mObservability: Superpowers for Developers
31mNo-Nonsense Observability Improvement
58mObserving Applications in Production
42mObservability Is Not Analytics!
