PagerDuty

Import PagerDuty incidents as Aegis incidents.

PagerDuty is where many operations teams are alerted and paged when a service fails. This connector reads those incidents into the Aegis incident register, so an outage that started as a page can be assessed, documented and, where needed, reported like any other incident. It reads only: Aegis does not create, acknowledge or resolve anything in PagerDuty.

At a glance

Direction Into Aegis.
What it brings in PagerDuty incidents, up to 100 per sync. Through the API you can limit a sync to incidents since a date or to chosen services; the button on the page has no such filter.
Where it lands Incidents, as system-outage incidents with PagerDuty as their source and the PagerDuty service as the affected system.
Credentials and permissions A PagerDuty REST API key (v2). Your PagerDuty subdomain is optional and is stored for reference only.
Owner of imported records The person who ran the sync.
When it runs On demand, from Sync Incidents on the connector page or through the API (POST /api/connectors/pagerduty/sync). There is no schedule.
Set it up /connectors/pagerduty, by people allowed to configure connectors, on a plan that includes the connector.

Who uses it

Admin Manager Managers and Admins can open the page, save the API key, test the connection and run a sync.

Contributor Viewer Contributors and Viewers are redirected away from /connectors/pagerduty. They work with the imported records in Incidents like any other incident.

What's on this screen

No screenshot of this page was captured for this edition. Reading from the top, the page shows:

Connect PagerDuty

  1. In PagerDuty, open Integrations › Developer Tools › API Access Keys and create a REST API key (v2). PagerDuty shows the key only once, so copy it straight away.
  2. In Aegis, open /connectors/pagerduty. Paste the key into API Key and, if you like, enter your subdomain (for example company from company.pagerduty.com).
  3. Select Save Configuration. A Configuration saved message appears and the status returns to Not Tested: saving never proves the connection.
  4. Select Test Connection. While it runs the label reads Testing.... On success the panel shows Connected to PagerDuty with whether any services and incidents were found and up to three of your account's abilities. On failure it shows Connection Failed with the reason.

To keep the saved key when you change only the subdomain, leave API Key blank; the hint under the field says so.

Import incidents

  1. After a successful test, select Sync Incidents. The status reads Syncing... while Aegis reads incidents from PagerDuty.
  2. When it finishes, Sync Results shows how many incidents were imported as new, updated, or skipped because nothing had changed. If the sync imported and updated nothing and reported errors, Sync Results does not appear; the status reads Connection Failed with the reason instead.
  3. Open Incidents to review the imported records. You are the owner of each new one.

Once the connector has synced, the page shows Last successful sync: with the date and time of the last completed sync, and it still does after a reload. The counts of a sync are shown only for the visit in which you ran it; the audit log records every sync.

How PagerDuty values are mapped

PagerDuty Aegis
Status triggered Status Open
Status acknowledged Status Investigating
Status resolved Status Resolved
Priority 1 / 2 / 3 / lower Severity Critical / High / Medium / Low
No priority: urgency high / low Severity High / Low

What a repeat sync does

Tips and limits

Where this connects

Incidents are handled in Incidents; regulatory reporting is covered in Incident reporting. For the other connectors, see Connectors.