PagerDuty
Import PagerDuty incidents as Aegis incidents.
At a glance
| Direction | Into Aegis. |
|---|---|
| What it brings in | PagerDuty incidents, optionally only since a date or for chosen services. |
| Where it lands | Incidents. |
| Credentials and permissions | A PagerDuty REST API key (v2) and your PagerDuty subdomain. |
| Owner of imported records | The person who ran the sync. |
| When it runs | On demand from the connector page or the API. |
| Set it up |
/connectors/pagerduty, by people allowed to configure
connectors, on a plan that includes the connector.
|
Good to know
-
If PagerDuty rejects the key, the connector switches to
Error; enter a new key and test again. - An imported incident still needs a person to assess whether it is a reportable breach.
Where this connects
Incidents are handled in Incidents.