1. Server Monitoring
  2. Process
  3. Outage assessment
Process · Outage assessment

Outage assessment

Tie interruption time and service impact to the incident being investigated.

Step by step

  1. Identify interruption Monitoring Operator

    The Monitoring Operator compares a failed check with the service, location and recent observations before opening an incident.

    • Show when and where failure was seen
    • Updates Availability checks, Services
  2. Record outage Incident Responder

    The Incident Responder enters the site code, outage reference and observed start time against the incident.

    • Anchor interruption to a case
    • Updates Service outages, Incidents
  3. Assess impact Service Owner

    The Service Owner marks the monitored service as delayed or unavailable and adds the degradation procedure where one applies.

    • Name the service effect and owner
    • Updates Service impacts, People
  4. Update investigation Incident Responder

    The responder records what the team tried and which locations or assets remain affected.

    • Preserve actions and status
    • Updates Incident updates, Incidents
  5. Confirm restoration Incident Responder

    A later successful check and owner review support the restoration time. The incident proceeds to resolution through the response process.

    • Record an observed recovery time
    • Updates Service outages, Availability checks
Monitoring Operator
Finds the observation; Incident Responder keeps the chronology; Service Owner confirms the impact and restoration.

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