Back to Docs

PagerDuty Integration

Set up incident-driven merge protection with PagerDuty webhooks and severity rules.

Overview

When PagerDuty fires an incident, Frost can automatically activate merge protection on the repositories you configure. When the incident resolves, protection lifts automatically. No manual intervention required.

1. Create the integration in Frost

  1. Navigate to your Organization in the Frost dashboard.
  2. Go to Incident Configuration.
  3. Click Add Integration and select PagerDuty.
  4. Frost will generate a webhook URL and a signing secret. Copy both.

2. Configure the webhook in PagerDuty

  1. In PagerDuty, go to Integrations → Generic Webhooks (v3).
  2. Click New Webhook.
  3. Paste the Frost webhook URL into the Webhook URL field.
  4. Select the events to subscribe to: incident.triggered and incident.resolved.
  5. Add a custom header: X-PagerDuty-Signature with your signing secret for webhook verification.
  6. Save the webhook.

3. Configure severity rules

Frost lets you control which incident severities trigger protection. By default, only P1 (critical) incidents activate protection.

  • P1 (Critical) — service is down, customers are impacted.
  • P2 (High) — significant degradation, high urgency.
  • P3 (Medium) — partial impact, moderate urgency.

You can adjust the minimum severity threshold per repository in the Incident Configuration settings.

4. Map PagerDuty services to repos

For precise control, map PagerDuty services to specific repositories. When an incident fires on a mapped service, only the associated repos get protected.

Without mappings, incidents from any service will protect all configured repositories in the organization.

5. Test the integration

  1. Create a test incident in PagerDuty.
  2. Verify the webhook is received — check the Incident History page in Frost.
  3. Confirm merge protection is active on the expected repositories.
  4. Resolve the test incident and verify protection lifts.

Troubleshooting

  • Webhook not received? — Verify the URL is correct and your PagerDuty webhook is active.
  • Signature verification failed? — Regenerate the signing secret in Frost and update it in PagerDuty.
  • Wrong repos protected? — Check your service mappings and ensure incident freeze is enabled per repo.
Frost Frost
Back to Docs