Incident priority allows you to classify incidents based on a level of prioritization. Just as alerts can have different severity levels and notifications can have different urgency levels, incidents can be classified into different priority levels. Priority labels are customized on a per-account basis, so you may configure the priority scheme in PagerDuty to match the scheme you may already be using in other tools.
- Establish an Incident Classification Scheme
- Configure Incident Priority
- Prioritize an Incident
- Disable Incident Priority
Before you configure incident priority, you should first establish an incident classification scheme. Your incident classification scheme establishes a common language and criteria for communicating about incident levels and response elements. This information is ideally shared organization-wide. It’s helpful to keep in mind that this scheme is not just for technical responders and support staff; other parts of your organization may need to be aware of incidents and their assessed impact, and occasionally participate in incident response, as well.
There are several steps to establishing an incident classification scheme:
- List the incident classification levels: This is frequently P1 through P5 (for priority), or SEV-1 through SEV-5 (for severity). Typically, the lower the number, the higher its impact (i.e., P1 is more important than P5).
- Define what each level means: Describe the impact and characteristics that apply for each classification level. These guidelines must be clear and objective enough that responders can accurately assess an open incident and assign exactly one level to it. That said, incidents may be upgraded or downgraded as the situation evolves.
- Define the expected response: For each classification level, identify the expected scope and response urgency. Some organizations have a formal or informal service level agreement per level, as well.
If your organization does not have an incident classification scheme in place, determining a small number of classification levels is essential for effective triage and major incident response processes. If, on the other hand, you have more than five classification levels, think critically about how many levels would benefit your organization in practice. The more levels you have, the more complex and time-consuming triage can become.
The Incident Priority feature does not allow any of the five levels to be blank. If your organization uses fewer than five classification levels, you can enter
---for any unused levels.
After establishing your incident classification scheme, the next step is to configure the levels in PagerDuty.
Required User Permissions
Account Owners and Admins/Global Admins can configure and edit Incident Priority levels.
To configure this feature, in the web app:
- Navigate to User Icon Account Settings Incident Priorities tab.
- You can classify incidents with five different priority levels. Customize your levels with the following:
|Priority Level||This is frequently P1 through P5 , or SEV-1 through SEV-5.|
|Color||Color labels are used to draw attention to the most important incidents in a dashboard or other view. We recommend using distinctive colors for the levels corresponding to major incidents; this boosts more important incidents’ visibility. For example, at PagerDuty we use red and orange for our two highest levels, and then blue and gray variations for less pressing incident levels.|
|Description||Describe the incident impact and characteristics that apply for each classification level. These guidelines must be clear and objective enough that responders can accurately assess an open incident and assign exactly one level to it.|
- Click Save.
Priority is displayed on the Incidents page, as well as on an incident's details page in both the web app and mobile app.
Prioritizing incidents helps drive decisions around the response process and also provides valuable context for other people. When looking at an incident, the priority gives an immediate and clear indication of prior assessment that has been performed. Incident priority can be set at the time of creation, or after the incident has been triggered. The following is an incident with a priority level set:
In addition, priority is clearly displayed on the incident dashboard, making it easy to see when critical issues are active. You can sort incidents by priority on this page, so that whether looking at incidents for a single team or across your whole organization, you can instantly see critical issues:
- Navigate to the Incidents page and click New Incident.
- Select your desired priority level from the dropdown.
- Enter remaining incident details, and click Create Incident.
- Find the incident that you would like to prioritize and select it’s Title to navigate to its details page.
- Click the Priority dropdown and select the desired priority level.
- Navigate to the Open Incidents screen, tap the overflow menu (top-right corner of screen) and select New Incident... .
- Tap Priority and select the priority level from the defined list.
- Enter any remaining incident incident details, and tap Create.
The incident will now have a label displaying its priority level:
- Find the incident that you would like to prioritize. Tap the incident’s name to navigate to its details screen.
- With the Triage tab selected, tap Edit Priority.
- Select a priority level.
- Tap Confirm in the confirmation dialog box.
In addition to the features available in the PagerDuty web app and mobile app, automated systems can also interact with incident priority. You can use the Incident REST API to specify an incident’s priority when it is created, and all relevant priority details are included when the API returns an incident object.
Please refer to our developer documentation for more information about working with incident priority:
Additionally, incident webhooks include information about an incident’s priority; please read our Webhooks Overview for more information.
Priority cannot be set from the Events API at this time.
Event Rules End-of-Life
Rulesets and Event Rules will end-of-life in 2024. We recommend using Event Orchestration instead, which offers new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting.
You can configure event rules to automatically add priority to an incident when it is created. Please read Set Priority with Event Rules for instructions and more information.
The Account Owner can disable incident priority in the web app:
- Navigate to User Icon Account Settings Incident Priorities tab.
- Click Disable Incident Priority Levels.
Note: Once disabled, your Incidents page in the web app not display a Priority column.
Retained Configuration Settings
After disabling incident priority, PagerDuty retains your configuration settings. In other words, if you choose to re-enable incident priority at a later time, your historical settings will be preserved and you will not need to configure them again from scratch.
Updated about 1 month ago