Practice English vocabulary for incident metrics: MTTD, MTTR, incident frequency by severity, dashboards, and tracking customer-impacting minutes.
0 / 5 completed
1 / 5
What is 'MTTD (Mean Time to Detect)'?
MTTD measures how quickly issues are discovered. A long MTTD means problems exist unnoticed, causing more customer impact. Improving MTTD involves better monitoring, alerting thresholds, and on-call responsiveness.
2 / 5
What is 'MTTR (Mean Time to Repair)'?
MTTR (sometimes called Mean Time to Resolve or Mean Time to Restore) measures how long it takes to fix incidents. Teams improve MTTR through runbooks, on-call training, better tooling, and faster communication processes.
3 / 5
What does 'incident frequency by severity' track?
Tracking incident frequency by severity reveals trends. If SEV-1 incidents increase quarter-over-quarter, systemic reliability issues need attention. If SEV-3 frequency is high but SEV-1 is low, the team is catching problems early — which is positive.
4 / 5
What does 'the incident dashboard tracks all open incidents' mean?
An incident dashboard provides a live, shared view of the operational situation. During peak periods with multiple simultaneous incidents, it helps incident commanders prioritize resources and prevents duplicate response efforts.
5 / 5
What are 'customer-impacting minutes per quarter' as an incident metric?
Customer-impacting minutes (or downtime minutes) is a business-facing reliability metric: (incident duration) × (fraction of customers affected). It translates technical incidents into business impact and is often reported to leadership alongside SLO compliance.