Dashboards and Runbooks: Scrapbooking for Engineers
summary
Claim: dashboards and runbooks usually hurt incidents because teams create knee‑jerk, hyper‑specific artifacts that pile up into an unsearchable scrapbook. Engineers spend 60 days every week across teams building/maintaining them; many dashboards are either over‑templated or single‑incident clones, many runbooks are either automatable or useless checkboxes. Uses Grafana screenshots and recommends composable tooling like Jsonnet and Pulumi, lifecycle rules for docs, automated runbooks and shifting toward traces/events for discoverability.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:33Welcome
- 1:20Story
- 2:47Feedback loop
- 4:16Scrapbooking
- 5:26Dashboards
- 7:27Over templating
- 9:26Runbooks
- 9:55Automation
related talks
45mCreating & Maintaining Impactful Dashboards'
11mModeling complex systems
14mWhat dashboards don't tell you
35mWho Needs Dashboards?
21mJourney from Broken Dashboards to O11y Maturity
44mIterative metrics, dashboards and monitors
24mObservability Through Users' Eyes and How To Fix the Knowledge Disc...
54mA Practical Guide to Dashboarding