Mean Time to Resolve (MTTR)
Mean Time to Resolve (MTTR): Time from incident start to resolution.
Also known as: MTTR
Formula
MTTR = Average of (Resolution time - Incident start time)Computable definition
The canonical formula in the GASP formula grammar. The MCP server compiles it to SQL over the datasets listed below.
(avg(field.resolved_at - field.started_at)) * 1440Unit: minutes
Breakdowns
by_severity: one row perseverityvalueby_incident_type: one row perincident_typevalue
Notes: Resolution time minus incident start time, in minutes. by_severity returns one row per severity because resolution targets are set per severity and a blended mean hides a slow sev1. by_incident_type separates incidents whose resolution paths differ, such as a security incident and a performance regression.
Data requirements
Grain: Per event · Frequency: Per deploy · Aggregation: event · Staged: no · Main source: Incident Management.
| Field | Dataset | Type |
|---|---|---|
resolved_at | incident | timestamp |
started_at | incident | timestamp |
Example SQL (Postgres)
SELECT ((SELECT AVG((EXTRACT(EPOCH FROM (resolved_at - started_at)) / 86400.0)) FROM incident WHERE started_at >= :period_start AND started_at < (:period_end + INTERVAL '1 day')) * 1440) AS mttr Access: recommended
sensitivity tier internal,
access scope department-scoped.
Guidance your policy engine enforces.
From an agent: with the GASP MCP server, call
lookup_metric({ "name": "Mean Time to Resolve (MTTR)" }) or generate_query({ "metric": "Mean Time to Resolve (MTTR)", "adapter": "<your adapter JSON>" }).
Benchmarks
- SEV1: < 1 hour
- SEV2: < 4 hours
- SEV3: < 24 hours
What It Tells You
Incident response capability.
Related Metrics
Connected in the GASP relationship graph.
Upstream: what drives this
- Deployment Frequency reduces MTTR (Engineering)