MTTR Trend is the page that turns a year of incident data into one chart. Mean Time to Resolution by service, by severity, by owner team, by time of day. Drill into any spike to see the contributing incidents. Use it for quarterly business reviews, retro discussions, and "are we getting better?" conversations with leadership.
The chart can slice by service (which service drove the regression), severity (sev-1 only vs sev-3+), owner team (which on-call rotation), or time of day (do nights have worse MTTR?). Stack two slices for richer queries: "MTTR for payments service during US daytime, sev-2 only." Save any slice as a named view that updates live.
Click any spike on the chart to see the contributing incidents. The drill-in panel lists them with severity, duration, the agent or human responder, and the postmortem link. Spikes that are dominated by one incident are usually outliers; spikes with five-plus contributors point at a systemic issue.
Set a target MTTR per service tier (e.g., tier-0 < 15m, tier-1 < 30m). The chart shows the target as a band; periods over the band are visually flagged. The targets are stored alongside SLOs in SLO Management so they version and review the same way.
For quarterly business reviews, export the current view to CSV with one click. The export includes the chart series, the slice metadata, and the contributing-incident counts so you can rebuild the chart in your slide tool of choice. Saved views also expose a stable URL that auto-updates if you embed the chart in a Notion or Confluence page.
Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.
Quarterly reviews used to mean a week of pivot tables. The MTTR Trend page is the pivot table, and it is always current.