Core concepts
SEV0 - Labeling your incident priority
Not all incidents are equal, it's important not only to get your team on the same page but everyone in your organisation. To achieve this as a organisation you need to agree how you claissifying incidents. This helps everyone understand the potential impact and how the incident should be addressed.
As an example we will use Severity Level or SEV for short.
SEV | Visible | Customer Impact | Communication | Page | Urgency |
---|---|---|---|---|---|
0 | Immediate | Site is down and all customers are impacted | Public Status Page | All staff, anyone who can help | All hours |
1 | Immediate | All customers are impacted | Public Status Page | All teams who are across the failing services | All hours |
2 | Partial | Some customers are impacted | Public Status Page | Teams who are across the failing services | All hours |
3 | No | Customers may be impacted but not visible | Internal Status Page | Teams who are across the failing services | Oncall / Business |
4 | No | Internal services but not visible | Optional | Handle as regular task item | Business |