Observability Through Users' Eyes and How To Fix the Knowledge Disc...
summary
Systems accumulate telemetry until costs and noise overwhelm operators, not because instrumentation is missing but because ownership and upkeep are. Empirical claims: dashboards often outlive the engineers who use them, alerts go unreviewed (about 25–29% report reviewing often while 15.3% report rarely), and scattered knowledge lives in one person. Fixes proven in practice: adopt a governance model, publish an internal library and runbooks, run joint office hours and observability champions per team. Improvements stick when processes enforce living documentation; regressions recur without continual care.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:23Speaker backgrounds
- 2:26Chaos in observability
- 3:06Perfect telemetry illusion
- 5:14Human interaction with telemetry
- 5:55Siloed knowledge problem
- 7:18Process and collaboration gaps
- 8:19Observability challenges
- 9:46Maintaining observability artifacts
- 12:34Fixing observability with governance
- 14:20Training and collaboration
- 15:24Observability champions
- 16:51Community standards
- 17:55New tools experiment
- 18:17Up-to-date observability artifacts
- 19:00Continuous observability improvement
- 20:03Incident response survey
- 22:35Community initiatives and closing
related talks
47mObservability - Holistic Quality across Software Systems
25mNo observability without theory
24mOperationalizing Observability: The Invisible Parts
38mThe Ticking Time Bomb of Observability Expectations
36mObservability? It's a Data Analytics Problem, You Fool!
20mI Can Sell You Observability, But You Can't Buy It
10mLightning Talk: Observability Debt: When Telemetry Stops Telling the Truth
32mEssential Software Observability for Every Role: Look No Further