- Incident Response — Incident volume, response times, and breakdowns by severity, environment, service, functionality, and type
- Workload — Hours worked across incidents and responders
- On-Call Metrics — Alert volume, acknowledgement, resolution, and response trends
Some default panels only appear when the related fields are enabled in your workspace configuration. For example, panels grouped by Functionality only appear when Functionalities are enabled.
Incident Response Dashboard
The Incident Response dashboard includes default metrics for incident volume, retrospectives, action items, response times, and incident breakdowns.Number of Incidents
Number of Retrospectives
Number of Action Items
Mean Time to Detection (MTTD)
Mean Time to Acknowledge (MTTA)
Mean Time to Mitigation (MTTM)
Mean Time to Resolution (MTTR)
Incidents by Severity
Incidents by Environment
Incidents by Service
Incidents by Functionality
Incidents by Type
Retrospectives by Cause
Note: The Incidents by Environment, Incidents by Functionality, and Retrospectives by Cause panels only appear when the related fields are enabled in your workspace.
Workload Dashboard
The Workload dashboard helps you understand time spent across incidents and responders.How Hours Worked Is Calculated
Every panel on this dashboard is built from one measurement, applied per person per incident: A person’s hours on an incident run from the moment they subscribe to it or join it, until the incident is resolved. If the incident has not been resolved, the clock runs to when it was cancelled, or to the present moment if it is still open. A negative result is floored at 0. The default panels use thehours_worked_until_resolved key. A custom panel built on hours_worked_until_mitigated stops the clock at mitigation instead, then cancellation, then the present moment.
Each panel then sums those per-person spans — across responders for a single incident, across incidents for a single responder, or across both for a team total.
Three things this measurement deliberately does not do:
- It does not infer activity. Someone subscribed to an incident accrues hours whether or not they posted, ran a command, or opened the incident. The metric measures attachment to an incident, not effort inside it.
- It does not cap a span. An incident nobody resolves for a week contributes a week of hours for everyone attached to it. A long-running incident with a large subscriber list produces large numbers, and that is the intended reading, not an anomaly.
- It does not adjust for time zones or working hours. Overnight and weekend time counts the same as time during a shift.