Incident Summaries

Catch up with ongoing incidents by viewing AI generated summaries

Are you looking at an incident midway and wondering what has happened so far? You can view AI generated summaries for incidents during any point of the incident lifecycle and quickly catch up with the timeline and progress that has been made, team members involved in triaging, resolution steps determined, meeting links to join war room discussions, and much more.

This feature is currently a beta offering. Feel free to share your feedback with us and we will be happy to engage and discuss the same. You can also optionally either upvote or downvote on the summaries generated for incidents and let us know via the prompt shown as to why you did not like the summary generated, in case of a downvote.

Note

Feature will be available for accounts in the

Generating Incident Summaries

Navigate to the details page of the incident you are interested in

Select Generate Summary

View the generated summary for the incident and optionally provide feedback

Understanding Incident Summaries

Each generated summary for an incident will have the following structure:

Timestamp of the time when the summary was generated
Status of the incident - Triggered, Acknowledged or Resolved
Impacted Service(s) - List of the impacted Service and it’s affected dependent Services
Incident Owner - We assign the impacted Service owner as the owner of the incident by default
Participants - List of responders for the incident
Timeline - AI summarised life cycle progress and updates of the incident so far
Resolution - AI summarised resolution reason and next steps determined (available only for incidents in the Resolved state)
Ability to provide feedback for the generated summary

You can simply click the copy icon to copy the incident summary in Markdown and use the same anywhere required.

Other Information

Incident summary can be generated for incidents in Triggered, Acknowledged and Resolved states
To keep information up to date with the progress of an incident, every time you want to view the summary for an incident, you can simply generate it using the steps above
Both user types - Users and Stakeholders can generate and view incident summaries given they are already added to the relevant Teams

PreviousAdditional Responders NextIncident Suggestions

Last updated 6 months ago

Was this helpful?

Understanding Incident Summaries

Each generated summary for an incident will have the following structure:

Timestamp of the time when the summary was generated

Status of the incident - Triggered, Acknowledged or Resolved

Impacted Service(s) - List of the impacted Service and it’s affected dependent Services

Incident Owner - We assign the impacted Service owner as the owner of the incident by default

Participants - List of responders for the incident

Timeline - AI summarised life cycle progress and updates of the incident so far

Resolution - AI summarised resolution reason and next steps determined (available only for incidents in the Resolved state)

Ability to provide feedback for the generated summary

You can simply click the copy icon to copy the incident summary in Markdown and use the same anywhere required.

Other Information

Incident summary can be generated for incidents in Triggered, Acknowledged and Resolved states

To keep information up to date with the progress of an incident, every time you want to view the summary for an incident, you can simply generate it using the steps above

Both user types - Users and Stakeholders can generate and view incident summaries given they are already added to the relevant Teams

Have any questions?.