Customizing Component Severities
Severities define the different states your components can be in. Customize them to match how you communicate status to your users.

What Are Severities?
Severities are the status levels for your components. Default examples include:
- Operational - Everything is working normally
- Degraded Performance - Slower than usual but functional
- Partial Outage - Some features unavailable
- Major Outage - Service is down
Each severity has a color that appears on your status page.
Default Severities
Your account comes with preset severities:
| Severity | Color | Meaning |
|---|---|---|
| Operational | Green | All good |
| Degraded Performance | Yellow | Reduced performance |
| Partial Outage | Orange | Some issues |
| Major Outage | Red | Complete outage |
| Under Maintenance | Blue | Planned maintenance |
Accessing Severity Settings
- Go to Severities in the left menu under Configuration
- Or find it in your account settings
Creating Custom Severities
To add a new severity:
- Click Add Severity or New Severity
- Enter a name (e.g., “Limited Functionality”)
- Choose a color
- Set the display order
- Click Save
Your new severity is now available for all components.
Editing Severities
To modify an existing severity:
- Click on the severity to edit
- Change the name, color, or order
- Click Save
Changes apply immediately to all components using that severity.
Severity Colors
Choose colors that communicate status clearly:
| Color | Typical Use |
|---|---|
| Green | All good, operational |
| Yellow | Minor issues, degraded |
| Orange | Partial problems |
| Red | Major issues, outage |
| Blue | Maintenance, informational |
| Gray | Unknown or unavailable |
Use consistent colors so users learn what each means.
Display Order
Severities can be ordered by severity level:
- Most severe at the top (e.g., Major Outage)
- Least severe at the bottom (e.g., Operational)
This order affects how severities appear in dropdown menus and reports.
Using Custom Severities
Once created, custom severities appear:
- When creating/editing incidents
- When manually setting component status
- In your status page display
Best Practices
| Do | Don’t |
|---|---|
| Use clear, simple names | Use technical jargon |
| Keep the list manageable (4-6 levels) | Create too many options |
| Use distinct colors | Use similar colors that confuse users |
| Order by severity | Randomly order the list |