The Metrics Question: Evolving Past MTTX
summary
Evolves MTTX by adding qualitative “data accessibility” from transcripts, Slack, Zoom and interviews to standard counts and MTTR so metrics become actionable. Shows 50 incidents averaging 55 minutes and a Thanksgiving DNS outage lasted five hours with 12 responders to connect numbers to root causes. Identifies recurring culprits (antiquated CI/CD, SQS, single-owner console), recommends making dashboards and runbooks widely available, proposing targeted rearchitecture and quarterly near‑miss analysis to secure executive sponsorship and measurable change.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 4:23Who are you
- 7:16Capturing the data
- 12:34Show your work
- 13:07Audience
- 14:11Story
- 14:52Example
- 16:50Sharing Analysis
- 17:48Example 1 Oldest CICD Pipeline
- 18:17Example 2 Centralized Communication Platform
- 18:47Adding Context
- 19:22Incidents
- 19:42Tips
- 21:10Last Thoughts
- 23:04Outro
related talks
45mHow To Measure MTTx Values in SRE
33mThe Problem with MTTR: Learning from Incident Reports
37mIncident Management Metrics That Matter
39mTest Metrics – a thread or a threat
41mAre We Getting Better Yet? Progress Toward Safer Operations
27mTales from the VOID: The Scary Truth about Incident Metrics
29mCulturing Resiliency with Data: A Taxonomy of Outages
10m⚡ Lightning Talk: Unlocking Customer-Centric Observability: A Case Study of OpenTelemetry To Reduce MTTD < 3 Mins