Working with incidents in SRM

Plan ahead of service disruptions and have SRM send notifications and create status when incidents occur. Distractions are minimized and teams stay focused on remediation.

You can manually create incidents within SRM or create an error budget action to do so. See Manually create an SRM incident or Create SLOs, SLIs, and error budget policies for more information.

• Manual creation from an alert.
• Manual creation from the incident view.
• Automatically from Alert automations, if Alert automations are installed.

The Assigned to field on an incident specify who should be notified. When a team is selected as a responder, team automations are checked to determine which schedule to use for the notifications.

注:

The Assigned to field is cleared when the Assigned-team or Service field is updated on an incident. Escalation policies for the newly assigned teams run. The field remains cleared until a user on the new team acknowledges an escalation notification.

If the Service is changed and the new Service does not have an assigned team, no changes occur.

When a service is deleted, its integrations, alerts, incidents, and automations are removed. Deleting a service isn't a recoverable action so consider deactivating the service instead.

Responders and above are notified for updates to incidents based on their notification preferences. If you made the update, you won't be notified.

You can resolve incidents by selecting specific incidents or in bulk. See Resolve an SRM incident, or Close an SRM incident or Cancel an SRM incident.

注:

Incidents in the Resolved state are automatically closed after 3 days.

For more information on the areas and fields available in an incident, see SRM incidents.

Export list information to a file from the list view.

Respond to an incident in the following ways:

• Tag an incident.
• Update the priority of an SRM incident.
• Set the state of the incident.
• Copy an SRM incident.
• Add a service to an SRM incident.
• SRM incidents.
• Resolve an SRM incident.
• Cancel an SRM incident.
• Close an SRM incident.
• Reopen an SRM incident.

• Manually create an SRM incident
  Create an incident if you think an issue poses a serious risk and should be taken care of as soon as possible.
• Reassign an SRM incident
  Reassign an incident to a responder when the incident tasks should be addressed by a particular team member.
• Update the priority of an SRM incident
  If the priority of an incident should be changed, you can manually update it to reflect its new criticality.
• Add a service to an SRM incident
  Add a service to an incident to increase the amount of data for the incident.
• Add resolution code and notes to an SRM incident
  Add a resolution code and notes to an incident when you have resolved the incident.
• Copy an SRM incident
  Copy an incident, if you have a similar issue.
• Resolve an SRM incident
  Resolve an incident, if you need it reviewed, or you think it has already been handled, but aren't ready to close it.
• Cancel an SRM incident
  Close an incident, if you think it is not an issue, or if it has already been handled.
• Close an SRM incident
  Close an incident when it’s not an issue or has already been handled.
• Reopen an SRM incident
  Reopen a closed incident if you think the issue is not yet resolved.