​

Overview

Severity helps you categorize the impact level of incidents. SEV0 incidents should be handled with priority over SEV3 incidents.

​

Field Type

Severity is strictly a select field type. This means only one severity value can be assigned per incident.

​

Attributes

Severities can be configured with the following attributes. Each severity attribute can be referenced via Liquid syntax.

​

ID

This is the unique identifier of the severity. This field cannot be customized. Rootly will auto assign the ID upon creation. It is typically used in Liquid references and API calls.

The following Liquid syntax will allow you to retrieve the severity ID that is selected for an incident:

{{ incident.severity\_id }}

OR

{{ incident.raw\_severity | get: 'id'}}

​

Name

This is the value that is displayed on the UI for the severity. This field is customizable.

The following Liquid syntax will allow you to retrieve the severity name that is selected for an incident:

{{ incident.severity }}

OR

{{ incident.raw\_severity | get: 'name'}}

​

Slug

This is the string that is used to reference the severity in Liquid references. This field is auto generated by lower-casing and hyphenating the severity name.

The following Liquid syntax will allow you to retrieve the severity slug that is selected for an incident:

{{ incident.severity\_slug }}

OR

{{ incident.raw\_severity | get: 'slug'}}

​

Description

This value is displayed on the UI to further explain each severity. This field is customizable.

The following Liquid syntax will allow you to retrieve the severity description that is selected for an incident:

{{ incident.raw\_severity | get: 'description'}}

​

Color

Each severity can be assigned a color, which will be used for color-coding on metrics graphs.

The following Liquid syntax will allow you to retrieve the severity color that is selected for an incident:

{{ incident.raw\_severity | get: 'color'}}

​

Slack Channels

Each severity can be linked to one or more Slack channels. By default, Rootly does not notify the linked channel(s) when a severity is selected for an incident. Notification needs to be explicitly called out as Attached Severity Channels in workflow configurations.

Systematically, each Slack channel is stored as an object containing an id and name.

The following Liquid syntax will allow you to list out the severity Slack Channel(s) that are selected for an incident:

{{ incident.raw\_severity | get: 'slack\_channels'}}

​

Slack Aliases

Each severity can be linked to one or more Slack user groups (aka aliases). By default, Rootly does not invite users in the linked user group(s) when a severity is selected for an incident. Invitations need to be explicitly called out as Attached Severity Aliases in workflow configurations.

The following Liquid syntax will allow you to list out the severity Slack Alias(es) that are selected for an incident:

{{ incident.raw\_severity | get: 'slack\_aliases'}}

​

Notify Emails

Each severity can be linked to one or more emails. By default, Rootly does not send emails to the linked address(es) when a severity is selected for an incident. Notification needs to be explicitly called out as {{ incident.raw\_severity | map: 'notify\_emails' | flatten | join: ',' }} in workflow configurations.

The following Liquid syntax will allow you to list out the severity Notify Email(s) that are selected for an incident:

{{ incident.raw\_severity | get: 'notify\_emails'}}

​

Support

If you need help or more information about this integration, please contact support@rootly.com or start a chat by navigating to Help > Chat with Us.