Learn
WebsiteLoginFree Trial
  • Incident Management
    • What is Incident Management? Beginner's Guide
    • Severity Levels
    • How to calculate MTTR and Other Common Incident Recovery Metrics
    • On-Call
    • SLA vs SLO vs SLI: What's The Difference?
    • Data Aggregation and Aggregators
  • DevOps
    • Best DevOps Tools for Each Phase of the DevOps Lifecycle
      • Best DevOps Planning Tools
      • Best DevOps Coding Tools
      • Best DevOps Build Tools
      • Best DevOps Testing Tools
      • Best DevOps Release Tools
      • Best DevOps Deployment Tools
      • Best DevOps Operations Tools
      • Best DevOps Monitroing Tools
    • What is DevOps?
      • Best CI/CD Tools
      • DevOps Infrastructure and Automation
      • What is a DevOps Pipeline?
      • DevOps Vs. Agile
      • Top 25 DevOps Interview Questions
      • What Are the Benefits of DevOps?
      • What is CI/CD?
      • What is a DevOps Engineer?
      • What is DevSecOps?
    • What is Observability?
      • USE and RED Method
    • What is Site Reliability Engineering (SRE)?
      • Four Golden Signals: SRE Monitoring
      • What is A Canary Deployment?
      • What is Blue-Green Deployment?
  • Docker
    • Overview
    • Dockerfile
    • Images
    • Containers
    • Storage
    • Network
    • Compose
    • Swarm
    • Resources
  • prometheus
    • Overview
    • Data Model
    • Metric Types
    • PromQL
      • Series Selection
      • Counter Rates & Increases
    • Pushgateway
    • Alertmanager
    • Remote Storage
Powered by GitBook
On this page

Was this helpful?

  1. Incident Management

Severity Levels

Not all incidents are created equal - categorizing incidents based on their impact will help your team resolved incidents faster.

PreviousWhat is Incident Management? Beginner's GuideNextHow to calculate MTTR and Other Common Incident Recovery Metrics

Last updated 11 months ago

Was this helpful?

What are severity levels?

Incident severity levels measure the impact an incident has on the business. Severity levels are useful for quickly understanding and concisely communicating the impact of an incident.

Incidents can be classified by severity, usually a "SEV" definition. Severities rank from SEV-1 to SEV-5. The lower the severity number, the more impactful the incident. Anything above a SEV-3 should automatically be considered a "major incident".

Always assume the worst - If you are unsure which severity an incident should be, treat it as the higher one.

Severity
Description
Example

SEV-1

Critical incident with very high impact.

A customer facing service is completely down for all customers.

SEV-2

Critical incident with significant impact.

A customer facing service is down for a subset of customers.

SEV-3

Minor incident with low impact.

Partial loss of functionality causing inconvenience to customers.

SEV-4

Minor issues requiring action, but not affecting customer ability to use the service.

Slower than average load times.

SEV-5

Cosmetic issues or bugs not affecting customer ability to use the service.

Application text is misspelled.

108KB
incident-severity-levels.pdf
pdf
Incident Severity Levels Cheat Sheet PDF
Incident Severity Levels Cheat Sheet