Manage an incident
Open Incidents to view active and historical incidents. Keeping incident state accurate is what makes escalation stop at the right moment and reporting mean anything.
Acknowledge an incident
- Open the incident from the notification, Incidents, or the mobile app.
- Review the severity, service and firing alarms.
- Select Acknowledge.
- Add a note saying you are taking ownership.
- Confirm the state changes to Acknowledged and escalation stops.
Acknowledgement records the user, time and note. Acknowledge before you start investigating — otherwise Shankh has no way to know the incident has been picked up and continues escalating.
Update the severity
- Open the active incident.
- Change the severity to match current impact.
- Save and confirm it appears in the severity history.
If an already acknowledged incident increases in severity, it can require re-acknowledgement and restart the applicable escalation path. Expect new notifications after raising severity.
Add a stakeholder update
- Open the active incident.
- Add a progress update — not an internal comment.
- State current impact, what is being done, and when the next update will come.
- Save the update.
- Open the incident's stakeholder live page and confirm it is visible.
Internal comments, progress updates, current impact and investigation notes can all be recorded, but only progress updates are intended for the stakeholder live page.
Resolve an incident
- Confirm the underlying condition has cleared and the alarms are no longer firing.
- Select Resolve.
- Record a resolution note describing the cause and the fix.
- Confirm the state changes to Resolved and escalation has stopped.
MTTA and MTTR are calculated from resolved incidents, so close incidents rather than leaving them active.
Reference: what the record holds
- Incident ID
- Workspace
- Service
- Severity
- Status
- Source
- Trigger time
- Current escalation state
- Acknowledgement details
- Resolution details
- Firing alarms
- Severity history