PagerDuty

Uses: Service Catalog Kong Gateway

The PagerDuty integration allows you to provide a way to alert the service team (via PagerDuty services), as well as provide information on current open incidents to consumers of the service directory. You can configure multiple instances of this integration, including multiple connections to the same third-party provider.

For each linked PagerDuty service, a summary will be provided on the Service Catalog service’s details page, showing current unresolved incidents and the current on-call user.

For a complete tutorial using the Konnect API, see Import and map PagerDuty resources in Service Catalog.

Authenticate the PagerDuty integration

  1. From the Service Catalog in Konnect, click Integrations.
  2. Select Add PagerDuty Instance
  3. Configure the Region, add authorization, and name the instance pagerduty. PagerDuty will ask you to grant consent to Konnect. Both Read and Write scopes are required.

Resources

Available PagerDuty resources:

Entity

Description

PagerDuty Service A PagerDuty service is any entity that can have incidents opened on it. In practice it could be a service, but could also be a group of services or an organization/team.

Discovery information

  • Automatic resource discovery is supported by this integration
  • Resource types: PagerDuty Service

Did this doc help?

Something wrong?

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!