Through its SaaS-based platform, PagerDuty empowers developers, DevOps, IT operations and business leaders to prevent and resolve business-impacting incidents for exceptional customer experience. When revenue and brand reputation depends on customer satisfaction, PagerDuty arms organizations with the insight to proactively manage events that may impact customers across their IT environment. With hundreds of native integrations, on-call scheduling and escalations, machine learning, business-wide response orchestration, analytics, and much more, PagerDuty gets the right data in the hands of the right people in real time, every time.
Compass currently supports PagerDuty as a tool to:
To integrate Compass with PagerDuty, you must first install the PagerDuty app in Compass. Then, you must create, or use an existing, PagerDuty API key (make sure it's a "full access" key) to connect Compass to the PagerDuty account to finish setup.
When you integrate an app with Compass, other Compass users can view events and metrics data sent from the app to Compass, even if they don't have access to that data in the underlying app. For example, when you integrate Bitbucket with Compass, someone who doesn't have access to a repository can see the events and metrics related to that repository in Compass. The same applies to data sent from this app to Compass.
Learn more about PagerDuty API keys
Integrate Compass with PagerDuty:
With the PagerDuty app Compass you can associate a PagerDuty service with a Compass component to show on-call and incident information directly in Compass. Compass evaluates the escalation policy associated with the specified service to render the on-call information. It will also watch for incidents belonging to the associated PagerDuty service to plot those on the activity feed and calculate incident-related metrics.
Your on-call information and metrics are displayed and updated from PagerDuty. If for some reason you encounter an error after adding a PagerDuty service, make sure you entered the right type of link (e.g. https://yourcompany.pagerduty.com/service-directory/POG79I7).
First be sure to complete the Add on-call and incident information from PagerDuty to a component section.
First be sure to complete the Add on-call and incident information from PagerDuty to a component section.
Supported metrics: Learn more about Compass metrics.
| Metric | Description | How it's calculated |
|---|---|---|
| Incident Count | The number of incidents opened in the last 28 days. | Incident events from associated PagerDuty service. |
| MTTR | MTTR (mean time to resolve) is the average time it takes to fully resolve a failure, as measured from when an incident occurs (making the component dysfunctional) to when the component becomes fully functional again, measured over the last 10 incidents. | Incident events from associated PagerDuty service. |
If you do not see metrics updating it could be that you have not had any incidents recently (hooray!). Make sure you also added the correct PagerDuty service link to the component.
The on-call information no longer appears in the on-call card.
Disconnecting your PagerDuty account means on-call and incident information will no longer be displayed for your components.
To disconnect a PagerDuty account from Compass:
If you no longer want to use the PagerDuty app from Compass you can uninstall it.
To uninstall the PagerDuty app from Compass:
Rate this page: