From dashboard soup to observability lasagna: Building better layers
summary
A concrete process claims to turn “dashboard soup” into a usable stack: a TDD-like predict, prove, measure loop with hands-on drills and quarterly game days. Load tests run with Graphana's K6 expose blind spots, leading to a four-layer lasagna (overview → system → logs → traces) with click-throughs, event logs for high-cardinality linking, capacity charts tied to six escalations workers, and user-observed delay panels (peaks ~2 seconds). Outcome: measurable dashboards, team adoption, and faster, reproducible debugging.
AI-written summary · about
chapters (16)
- 0:00Observability transformation intro
- 1:45Reliability needs observability
- 3:11Problem with dashboard soup
- 4:37Observability with TDD
- 6:01Predicting system behavior
- 7:48Proving predictions with load tests
- 9:34Measuring dashboard metrics
- 11:43Observability lasagna layers
- 13:07Quick triage dashboard
- 15:58Deep debugging dashboards
- 17:01Logs and traces insights
- 18:46Better dashboard tips
- 20:52Metrics to logs context
- 21:53Visualizing capacity limits
- 23:18Team observability collaboration
- 24:44Key takeaways
related talks
11mModeling complex systems
21mJourney from Broken Dashboards to O11y Maturity
49mA Practical Guide to Dashboarding
31mCharting New Frontiers: The Evolution of Observability in Cloud Environments
46mObservability engineer, the best friend you never knew you had
31mObservability for Developers: How to Get There
54mA Practical Guide to Dashboarding
32mEssential Software Observability for Every Role: Look No Further