ITSM tools typically excel at ticketing-related workflows and are used to create and track all customer and service-desk-reported incidents. This being said, ITSM tools don’t usually have effective response capabilities, particularly for critical-impact incidents requiring urgent response. Because of this, PagerDuty’s extensive incident response capabilities are commonly used to augment an ITSM tool deployment. In this configuration, certain incidents in the ITSM tool are sent to PagerDuty, at which point PagerDuty’s coordinated response and stakeholder communication features can be used.
PagerDuty integrates with a number of ITSM tools, including:
Many of the ITSM tool integrations also synchronize bidirectionally with PagerDuty, updating the originating ITSM ticket with information on escalations, re-assignments, priority changes, state changes, and notes.
- Ticketing integrations: Jira Cloud and Jira Server are available on our Professional, Team (legacy), Business, and Digital Operations plans.
- Advanced ITSM integrations: ServiceNow and Cherwell are only available on our Business and Digital Operations plans.
Please contact our Sales Team if you would like to upgrade to a plan featuring the above integrations.
ITSM systems often don’t integrate well with monitoring tools, as they are inherently designed to work with human-speed data, rather than the machine-speed data flows that monitoring tools generate. In cases where ITSM systems are used with monitoring tools, it often results in a “swivel-chair” workflow: a user works directly with a monitoring tool, and when they determine an incident is occurring, they switch applications and manually create a ticket in the ITSM system, using clipboard cut-and-paste to move the data over. This workflow is cumbersome, error-prone, and provides no direct linkage between operational data and ITSM tickets.
Using PagerDuty to integrate monitoring tools and ITSM systems results in an improved workflow. Integrating a monitoring tool with PagerDuty is very simple, and can often be completed in just a few minutes. Once the monitoring tool is integrated, events will be sent to PagerDuty, where they can be routed to services and turn into an incident, have event rules applied, be filtered out if appropriate, and much more. Any incident that requires attention will be automatically assigned to the appropriate responder according to scheduled on-call rotations. For straightforward issues, the initial responder can handle the issue directly; in other cases the responder will triage the incident and classify it using the established incident priority levels.
At this point, many organizations will want to have an ITSM ticket created to track the incident. Instead of creating a ticket manually, the responder can simply click a button within PagerDuty to create an ITSM ticket.
After the ITSM ticket is created, the PagerDuty incident and ITSM ticket are linked, and updates to the PagerDuty incident will be reflected in the ITSM ticket. This is beneficial in many ways:
- Incident response orchestration: PagerDuty has response mobilization, stakeholder communication, and other response orchestration capabilities, all of which can be leveraged directly from the PagerDuty incident.
- Data linkage: For review and reporting purposes, the ITSM ticket is linked to the PagerDuty incident, which in turn is linked to the underlying monitoring tool alerts. This linkage makes post-incident analysis, including postmortems, much more efficient.
- Auto-resolution: If the monitoring tool detects that the underlying issue has recovered, the corresponding PagerDuty incident will receive this update, resolve itself, and then reflect that resolution to the ITSM ticket.
- Minimized noise: The right tickets are created in the ITSM system, rather than too many (if monitoring tool alerts are fed directly in) or too few (if manual ticket creation is the norm).
Updated 9 months ago