Course contentsShow
← Cloud and Infrastructure
Lesson 2129 of 2,98945. Observability - Dashboards and SLOsFree lesson

Incident Severity Levels

Define severity classifications (P0-P4) and the appropriate response procedures for each level.

Incident Severity Levels

What you'll learn: How to classify incidents using severity levels (P0-P4) and match each level to the right response procedures.

Why Severity Levels Matter

Not all incidents are created equal. A complete service outage affecting all customers demands immediate, all-hands response, while a minor UI bug might wait until business hours. Severity levels provide a shared language for your team to quickly assess impact and mobilize the appropriate resources.

Think of severity levels like hospital triage: life-threatening emergencies go straight to the trauma bay, while minor injuries can wait. The classification determines urgency, not just importance.

The Standard Severity Framework

Most organizations use a P0 through P4 scale (P = Priority):

P0 (Critical): Complete service outage or data loss affecting all or most users. Revenue-impacting. Response: immediate page-out, war room, executive notification. Resolution target: minutes to hours.

P1 (High): Major functionality degraded or significant user segment affected. Core features unavailable. Response: page on-call engineer, assemble incident team. Resolution target: hours.

P2 (Medium): Partial service degradation, workarounds exist, or minor feature broken. Response: notify on-call, address during business hours if off-hours. Resolution target: same day or next business day.

P3 (Low): Minor issues, cosmetic bugs, or non-urgent operational tasks. Response: create ticket, prioritize in backlog. Resolution target: days to weeks.

P4 (Minimal): Feature requests, documentation issues, or "nice-to-haves." Response: log and triage during planning. Resolution target: weeks to months or defer.

Applying Severity Levels

When an alert fires, consult your error budget status and SLO burn rate. A P2 might escalate to P1 if you're already depleted. Clear severity definitions prevent analysis paralysis and ensure your on-call rotation knows exactly when to wake people up at 3 AM.

Key Takeaway: Severity levels (P0-P4) translate incident impact into clear response protocols, ensuring the right people respond with the right urgency—protecting both your service and your team's sanity.