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
- Incident response
Incident response
Move a service observation into an owned incident with a readable response chronology.
Step by step
-
Observe service Monitoring Operator
The Monitoring Operator reviews a failed availability check and recent resource samples for the affected service and asset.
- Preserve check and sample times
- Updates Availability checks, Server samples
-
Open incident Monitoring Operator
The operator records a summary, priority, service, asset and assignee, then leaves the incident open for the named responder.
- Identify affected service and owner
- Updates Incidents, Services, Assets
-
Acknowledge Incident Responder
The Incident Responder accepts the case, records the acknowledgment time and a response event, and changes the incident state to acknowledged.
- Record the receiving responder
- Updates Incidents, Response events
-
Investigate Incident Responder
The responder enters an attributed update describing the evidence, the action taken and what remains uncertain. Further response events mark escalation or mitigation.
- Build the attributed chronology
- Updates Incident updates, Response events
-
Resolve Incident Responder
Once the service result is checked, the responder records a resolution event and time. The Service Owner reviews the history before closure.
- Preserve recovery time and action
- Updates Incidents, Response events
Who does what
Roles and permissions- Monitoring Operator
- Opens and routes the case; Incident Responder owns investigation; Service Owner reviews the outcome.
Set up Server Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.