These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Server Monitoring
- Process
- Service recovery
Service recovery
Check restored service behavior before resolving and closing the incident.
Step by step
-
Review action Incident Responder
The Incident Responder reads the last incident update, response events and any deployment result before claiming recovery.
- Identify the last attempted fix
- Updates Incident updates, Response events, Deployments
-
Check service Monitoring Operator
The Monitoring Operator reviews a new availability result from the relevant probe location and recent samples for the affected asset.
- Preserve post-action observations
- Updates Availability checks, Server samples
-
Record restoration Incident Responder
The responder fills the outage restoration time when the interrupted service has returned and adds an update describing the evidence.
- Mark interruption end and impact
- Updates Service outages, Service impacts
-
Resolve incident Incident Responder
The responder records a resolve event and resolution time after checking the service and impact.
- Record resolution state and time
- Updates Incidents, Response events
-
Close review Service Owner
The Service Owner reads the chronology, confirms the outcome and closes the incident.
- Confirm owner review
- Updates Incidents, Services
Who does what
Roles and permissions- Incident Responder
- Documents recovery; Monitoring Operator checks observations; Service Owner reviews closure.
Set up Server Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.