Skip to content
Slipwaydocs

PagerDuty

Change events as deploy markers and incidents on failure.

At a glance

Section titled “At a glance”
Category Incident management
Authentication Events API v2 routing key
Provider id pagerduty

What it does

Section titled “What it does”
  • Change events on deploy
  • Trigger incident on failed or rolled-back deployment

Set up

Section titled “Set up”
  1. Create an API key or integration key in the incident tool.
  2. Add the integration in Slipway and map services to incident-tool services.
  3. Create a subscription for deployment.failed and deployment.rolled_back.

Configuration

Section titled “Configuration”

Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.

provider: pagerduty
config:
  routing_key_secret: PAGERDUTY_ROUTING_KEY
subscription:
  events: [deployment.failed, deployment.rolled_back]
  severity: error
Section titled “Related”