Observability can help you understand change
summary
Observability claims that observability is the practice of understanding change in distributed systems, not just prettier dashboards. It uses concrete data — metrics logs and traces — and automated analyses that correlate causes (service versions, config pushes) with effects (slow vs fast transactions) so teams find the real culprit. Practical advice: instrument with OpenTelemetry, set SLOs to focus what matters, and run continuous, end-to-end analysis instead of ad hoc dashboards.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:41WHAT IS DEVOPS?
- 17:46Observability is...
- 20:05Incident response, circa 2001
- 23:16Change, change, change
- 24:46Connecting causes and effects
- 27:20From monitoring to observability
related talks
35mObservability: Building Confidence & Answering the What, Where, How
29mObservability; a gentle introduction
36mObservability? It's a Data Analytics Problem, You Fool!
30mObservability is More than Logs, Metrics & Traces
42mObservability Is Not Analytics!
08m“Observability for testers”
48mObservability or How to Know the State of Your System
39mThe 5W’s of Observability with Practical Examples