Incidents · Free+
Incident metrics dashboard
The view ops leads ask for at every weekly review: "how fast did we resolve, how fast did we communicate, what's getting worse?" Pre-built so you stop screen-shotting spreadsheets.
Why you need it
Most status-page tools surface incidents but not the shape of how you handle them. The metrics dashboard puts the operator-facing reliability story in one screen so the data lives next to the workflow that produced it.
- Mean time to resolve. Average
ResolvedAtUtc − OpenedAtUtcacross resolved incidents in the window. Excludes still-open + post- mortem-only states so the metric reflects fix time, not comms tail. - Time to first update. Average delay from incident open to first public update. Auto-incidents that post their seed update at open weigh this optimistically by design — it reflects subscriber-perceived responsiveness.
- Volume trend. 12-bucket bar chart. Weekly buckets for 30 / 90-day windows, monthly for 365-day. Tooltips per bar; bars colour-coded by count.
- Most-incident-involved components. Top 5 monitors by IncidentComponent link count in window. Honest about the metric: it counts links not unique incidents, so a multi-component outage weighs each component equally.
Where it pays off
One dashboard, several rituals:
- Weekly ops review. Pull up the 30-day window before the meeting — five seconds of "are we getting better or worse" without prep.
- Quarterly board update. 365-day window screenshot for the slide on platform reliability.
- Triaging investment. Top components tell you where to spend the next reliability sprint.
Available on Free+. Already on StatusPulse? See the full config in Help →
Related
Try Incident metrics dashboard in StatusPulse
5 probes, 1 status page, forever. No credit card. US or EU host — you choose.