1. Server Monitoring
  2. Process
  3. Service recovery
Process · Service recovery

Service recovery

Check restored service behavior before resolving and closing the incident.

Step by step

  1. 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
  2. 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
  3. 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
  4. 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
  5. Close review Service Owner

    The Service Owner reads the chronology, confirms the outcome and closes the incident.

    • Confirm owner review
    • Updates Incidents, Services
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.

How to get started