To observe or Not, is not the question
summary
Claim: observability only matters when it produces actionable answers tying system health to business outcomes. Describes collecting logs metrics traces and using real user monitoring and synthetic checks, tracking request duration and API latency, and labeling telemetry by user region plan and feature flag. Shows a concrete case of a 5xx spike in checkout that correlates to revenue drop and justifies canary rollback. Emphasizes composite SLOs, correlation and unified dashboards that actually reduce mean time to resolution.
AI-written summary · about
chapters (9)
- 0:00Introduction and Welcome
- 1:02Understanding Observability
- 1:57Technical Context of Observability
- 3:06Operational Context and Dashboards
- 4:10Developer Experience and DevOps
- 5:10User Experience and Business Perspective
- 7:39Security and Compliance
- 9:33Correlation of Metrics
- 16:56Conclusion and Summary
related talks
42mObservability can help you understand change
42mObservability Is Not Analytics!
29mObservability; a gentle introduction
36mObservability? It's a Data Analytics Problem, You Fool!
30mObservability is More than Logs, Metrics & Traces
06mIgnite: Observability Observed
32mThe Role of Observability in Cloud Native Environments
13mObservability that matters