Skip to main content
Manage incident severities. Each incident has a severity, picked from one of the severities configured in your organisations settings. Severities help categorise incidents, and communicate urgency/impact. You can use severities when filtering incidents in the dashboard, and in workflows and announcement rules.

​
The severity object

​
created_at
string<date-time>
required

When the action was created

Example:

"2021-08-17T13:28:57.801578Z"

​
description
string
required

Description of the severity

Example:

"Issues with **low impact**."

​
id
string
required

Unique identifier of the severity

Example:

"01FCNDV6P870EA6S7TK1DSYDG0"

​
name
string
required

Human readable name of the severity

Maximum string length: 50
Example:

"Minor"

​
rank
integer<int64>
required

Rank to help sort severities (lower numbers are less severe)

Example:

1

​
updated_at
string<date-time>
required

When the action was last updated

Example:

"2021-08-17T13:28:57.801578Z"