-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #17 from mt-sre/mhull-mtsre-867-incident-management
add incident management documentation
- Loading branch information
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
22 changes: 22 additions & 0 deletions
22
content/en/docs/internal-documentation/incident-management.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
title: Incident Management | ||
linkTitle: Incident Management | ||
--- | ||
|
||
Preparedness for major incidents is crucial. We have established the | ||
following Incident Management processes to ensure SREs can follow predetermined procedures: | ||
|
||
- [Incident Management Process](https://source.redhat.com/groups/public/service-delivery/service_delivery_wiki/incident_management_process) | ||
|
||
- [Incident Response Cheatsheet](https://github.com/openshift/ops-sop/blob/master/policies/incident_response.asciidoc) | ||
|
||
- [Automated Incident Management Process (WebRCA)](https://source.redhat.com/groups/public/service-delivery/service_delivery_wiki/automated_incident_management_process) | ||
|
||
## Coverage | ||
|
||
Layered Products SRE (LPSRE) provides 24x7 coverage and support. | ||
|
||
If you need to escalate an incident, please refer to the | ||
[Layered Products SRE Escalation Procedure](https://source.redhat.com/groups/public/sre/wiki/cs_sre_escalation_procedure). | ||
|
||
**NOTE:** Only escalate an incident if the standard manual notification process using an OHSS ticket has failed. |