118
edits
Incident Handling: Difference between revisions
Jump to navigation
Jump to search
→Checklist
No edit summary |
|||
| Line 29: | Line 29: | ||
## Mark Zulip topic as resolved if no other incidents for the host. | ## Mark Zulip topic as resolved if no other incidents for the host. | ||
## Check for related triggers and resolve them. | ## Check for related triggers and resolve them. | ||
## If there were any SRE - Report threads | ## If there were any SRE - Report threads: | ||
### post a summary describing the high-level incident, that it is resolved and how it was resolved. | ### post a summary describing the high-level incident, that it is resolved, and how it was resolved. | ||
### post that summary message to any client channels such as Slack too. | ### post that summary message to any client channels such as Slack too. | ||
### close the thread in SRE - Report | ### close the thread in SRE - Report | ||
Note: we do not accept discussions on the how or why of incident response in the SRE - Report channel; those should be redirected to either Retro or Organisational channels. The only reason to reopen a thread in SRE - Report should be to report that there's still impact and the incident has been resolved prematurely. | |||
=== Non-Critical Incidents === | === Non-Critical Incidents === | ||