Incident timing
Which services have incidents that stayed open longest, and when were they acknowledged and resolved?
Read incident timing, coverage, problem work and intake exceptions.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Open | 27 | ||
| Acknowledged | 20 | 74% | |
| Investigating | 14 | 70% | |
| Resolved | 8 | 57% |
Sample counts per stage
Which services have incidents that stayed open longest, and when were they acknowledged and resolved?
Which actions were recorded for a disruption, and who took them?
Which service has scheduled responders for the period under review?
Which recurring issues remain open or known errors by service and owner?
Which approved changes have a planned window, and what was verified or rolled back?
Which monitoring provider receipts were rejected or failed?
Count incidents by priority and service across opened dates.
Compare opened, acknowledged and resolved times for each incident.
Group response events and their responders under each incident.
Review on-call shift start and end times, responder and escalation level by service.
Group problems by service, owner and current status.
Compare scheduled start and end dates with risk and status.
Review service requests by due date, completion date and status.
Group integration receipts by provider and handling status.
Start free, then use Proto to change fields, steps and approvals before your team goes live.