Observability in Practice: How to Become Proactive with Bugs
summary
Practical observability techniques using Sentry or GlitchTip for full error context (stacks, variables, occurrence counts), Metabase SQL-based data alerts that caught a signup DoS, Mixpanel event/funnel tracking that revealed conversion fall from ~90% to ~30%, and Backstop pixel-diff visual regression checks. Also presents a small event-store endpoint carrying trace/session IDs, hours-to-deploy setup with Slack alerts, and a process change requiring PRs to state how fixes will be observed — measures that reduced detection and repair time.
AI-written summary · about
chapters (10)
- 0:00Observability introduction
- 10:16Logs to monitoring platforms
- 13:06Error alerts fail
- 16:59Data-driven alerts with Metabase
- 21:11Event-driven observability
- 26:51Implementing event system
- 30:04User observability with Mixpanel
- 35:14Visual regression with BackstopJS
- 39:06Team process integration
- 43:38Value from observability
related talks
29mObservability for Developers: How to Get From Here to There
22mFrontend Observability Odyssey
31mObservability for Developers: How to Get There
31mObservability driven development
29mObservability; a gentle introduction
38mOff the Beaten Path: Moving Observability Focus from Your Service
53mUnmask hidden issues with Observability superpowers!
44mObservability: Superpowers for Developers