In ServiceNow, go to System Applications → Applications → Downloads tab and find the application PagerDuty Incident Resolution Platform. Under the application title, you will see the version of the app.
By default, the PagerDuty application triggers a PagerDuty incident if the service and escalation policy used for handling the incident can be determined, and if the incident’s priority is either P1 or P2.
However, this can be updated, in ServiceNow Configuration Files Business Rules Open PD Trigger PagerDuty Incident Business Rule:
By default, the priorities 1 - Critical and 2 - High will be selected. If you wish to trigger PagerDuty incidents for other priorities as well, simply multi-select any combination of the priorities you desire and this will create respective PagerDuty incidents for all priorities selected. If you do make an edit to the priorities that trigger PagerDuty incidents, you will likely also want to make the same adjustment to the priority condition of a second business rule, PD Trigger PagerDuty Incident on update, which covers scenarios in which an already existent ServiceNow incident (not yet linked to PagerDuty) is updated such that conditions are met to create a PagerDuty incident.
Before proceeding with the above, ensure that PagerDuty Priorities and ServiceNow Priorities have been synchronized and configured as per this guide.
Please note that any customizations which alter the integration’s out-of-the-box behavior will not be supported by the PagerDuty Support Team. However, we appreciate that it may be necessary to configure the synchronization between incidents for more priorities overall, including P1 and P2.
The service and escalation policy are determined as follows:
- If the ServiceNow to PagerDuty mapping is set to “Assignment Groups map to PagerDuty”: the assignment group must be provisioned, i.e. its PagerDuty Service and PagerDuty Escalation fields must be set to valid IDs of PagerDuty service and escalation policies, respectively;
- If the ServiceNow to PagerDuty mapping is set to “Configuration Items and Assignment Groups map to PagerDuty”:
- The escalation policy can be determined from the assignment group, whether it is set as the assignment group of the incident or as the assignment group designated for the configuration item;
- The service can be determined from the configuration item, OR:
- If the configuration item is not provisioned, the service can be determined from the configuration property “Default PagerDuty Service ID to use if Configuration Item is not mapped” (this is a catch-all)
In versions 3.5 and earlier:
The PagerDuty escalation policy is not required when creating the incident, but only assignment groups can be associated with PagerDuty services.
As of version 4.0, there are three fields for PagerDuty on the group form:
two fields on the incident form, one field on the user form and one field on the configuration items form.
To make each one visible:
- When viewing the form you want to change, right click the grey header,
- Select Configure → Form Layout. The new page will have two columns.
- Look for the PagerDuty field(s) you want in the left column, select it and click the right arrow to add it.
- Save once complete. Go back to the form and you should see the new field(s) added.
You can also enable the fields in the list view; click on the gear icon in the upper left corner of the list to add the columns to the display.
Right click on the field label, click Configure Dictionary, uncheck Read only on the new page, and save.
This will allow you to reset provisioning of a user, group or configuration item.
- Enable writing to the integration fields as described above. The fields' labels all start with "PagerDuty", and their column names all start with
- Set the values of the fields to blank.
- Delete or rename the corresponding objects in PagerDuty to avoid name collisions, with the exception of users.
Objects must have unique names, ignoring differences in case and leading/trailing whitespace differences, which can cause errors when trying to provision them again, with the exception of users. Thus, step 3 is necessary to ensure there are no preexisting objects in the PagerDuty account with the same name.
The reason why this isn't necessary for users is because the integration does not attempt to create a new user if it can find a user with the same email address as the user in ServiceNow. Thus, existing users will not cause issues when provisioning.
If you clear out the value of the PagerDuty Webhook field in the ServiceNow assignment group / configuration item, then a webhook will be automatically re-provisioned in PagerDuty at the time of the next incident in this group / for the CI that triggers in PagerDuty, and the integration will then save the new webhook object's ID to this field.
Whilst the usual out-of-the-box mapping is 1-to-1, it is however, possible to map many PagerDuty Services to single ServiceNow Assignment Group or CI's more information here
The fields such as PagerDuty Escalation and PagerDuty Service that are added to the assignment group, configuration item and user tables in ServiceNow are automatically populated with IDs from PagerDuty when provisioning them. These IDs are all upper-cased alphanumeric strings that begin with
P. The ID of any object can be obtained by navigating to view the object in PagerDuty, and examining the page URL. The ID should be near the end of the URL.
How do I tie an assignment group or configuration item to a preexisting escalation policy or service?
To "manually" provision (i.e. create a link between preexisting objects in both PagerDuty and ServiceNow):
- Clear out the values that contain the PagerDuty IDs, i.e. PagerDuty Escalation, PagerDuty Service etc.
- Obtain the values of the object IDs from their respective view pages in PagerDuty
- Put the ID values into the respective fields in the ServiceNow object (assignment group or configuration item) and save
The following values are sent when provisioning:
- Display value (i.e. full name)
- Phone numbers
No, not at this time. You can integrate a single PagerDuty instance with multiple ServiceNow instances, but you cannot integrate multiple PagerDuty instances with a single ServiceNow instance.
Updated about a month ago