Incident priority allows the classification of incidents based on a level of prioritization. Just as alerts can have different levels of severity and notifications can have different levels of urgency, incidents can be classified into different levels of priority. Priority labels can be customized on a per-account basis so you can match to your existing priority scheme that may be in use in other tools.
Ideally shared organization-wide, your incident classification scheme establishes common language and criteria for communicating about levels of incidents and elements of response. 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 need to participate in incident response, as well.
There are several parts 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 indicated impact.
- Define what each level means: 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. However, the incident may be “upgraded” or “downgraded” as the situation evolves.
- Define the expected response: For each classification level, the expected scope and response urgency must be identified. Some organizations have a formal or informal service level agreement per level, as well.
For an example and additional details on the above, see the PagerDuty Incident Response Guide.
Many organizations already have an incident classification scheme in place. If you don’t, putting a small number of classification levels in place is essential for an effective triage and major incident response process. If, on the other hand, you have more than 5 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 becomes.
When using less than 5 classification levels, you can enter
---in the remaining levels in order to utilize the incident priority classification levels. It is not possible to leave any levels blank when enabled.
When you have identified the incident classification levels you will be using, the next step is to configure PagerDuty to support those levels. Once enabled, the UI of your incident dashboard will change to include the Priority column account-wide.
To enable this feature:
- Navigate to User Icon Account Settings Incident Priorities tab.
- Click Enable Incident Priority Levels.
- You can classify incidents with 5 different priority levels. Customize your levels with the following:
- Priority Level: This is frequently P1 through P5 (for priority), or SEV-1 through SEV-5 (for severity). Typically, the lower the number, the higher its indicated impact.
- Color: Color labels are used to draw attention to the most important incidents in a dashboard or other view. It’s best to use distinctive colors for the levels corresponding to major incidents for immediate recognition and visibility. For example, at PagerDuty we use red and orange for our two highest levels, and then blue and grey variations for lesser 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 when finished.
When you return to the Incidents page, you will see that the dashboard now contains a column for Priority. The priority is also displayed in an incident's details in both the web UI and mobile app. By default, past incidents will not have a priority, but you can append a priority to a past incident from the incident details page.
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:
To set priority at incident creation:
- Navigate to the Incidents page and click New Incident.
- Select the priority level that you would like from the dropdown:
- After completing your other incident details, click Create Incident.
To edit an incident's priority after it has been triggered:
- Find the incident that you would like to prioritize. Click the name of the incident to open its details.
- Click the Priority dropdown and select the priority level. This will automatically update the incident’s priority for all users across the account.
- Navigate to the Open Incidents screen, tap the overflow menu (top-right corner of screen) and tap New Incident... .
- Tap Priority and select the priority level from the defined list.
- After completing your other incident details, click Create. The incident will now have a label denoting its classification:
To edit an incident's priority after it has been triggered:
- Find the incident that you would like to prioritize. Tap the incident name to open the details.
- Tap the overflow menu and tap Add Priority.
- Select the priority level from the screen.
- Tap Confirm in the confirmation dialog box to change the priority.
In addition to the features available within the PagerDuty web app, incident priority can also be used in automated systems. The incident REST API can be used to specify the priority for an incident when it is created, and all relevant priority details are included with incident objects returned from the API. You can learn more about how to retrieve the configured incident priority scheme and create incidents with priority in our developer documentation.
Additionally, incident webhooks include full information about that incident’s priority; details are available here.
Priority cannot be set from the Events API at this time.
You can also configure event rules to automatically add priority to an incident when it is created. Please read Setting Priority with Event Rules for instructions and more information.
Updated about a month ago