Skip to main content
Connect PagerDuty to page your on-call responders when a data issue opens.

​
How it works

Issues from monitors and from transformation layer tests (dbt, SQLMesh, or Coalesce Transform) are sent to PagerDuty as alerts. Each alert carries the error message, the downstream impact such as affected data products, and links to the issue. Status changes sync both ways, see Syncing the status.

​
Requirements

  • You need the Admin base role in PagerDuty to set up the integration. If you do not have it, ask an Admin or Account Owner in your organization.

​
Checking that alerts arrive

Every alert Coalesce Quality sends to PagerDuty is recorded under Settings > Integrations > your PagerDuty integration > Deliveries: the request made to the PagerDuty Events API, the response it returned, and the reason when nothing was sent. Use Send test event to send a test alert and see the outcome, and Redeliver to send an earlier event again once you have changed something. A wrong or rotated Integration Key shows up there as a rejected request rather than as silence, which is the usual reason alerts stop arriving. Each delivery also carries the PagerDuty dedup_key, so an incident on the PagerDuty side can be traced back to the delivery that opened it. See Debugging Deliveries.

​
Support

If you need help with this integration, ask in your shared Slack channel with us, or email support@coalesce.io.

​
Integration Walkthrough

​
In PagerDuty

  1. There are two ways to integrate with PagerDuty: via Global Event Routing or on a PagerDuty Service. If you are adding this integration to an existing PagerDuty service, please skip to the Integrating with a PagerDuty Service section of this guide.

​
Integrating With Global Event Routing

Integrating with Global Event Routing enables you to route events to specific services based on the payload of the event from your tool. If you would like to learn more, please visit our article on Global Event Routing.
  1. From the Configuration menu, select Event Rules.
  2. On the Event Rules screen, click on the arrow next to Incoming Event Source to display the Integration key information. Copy your Integration Key. This is the same integration key you will use for any other tool you want to integrate with using event rules. When you have finished setting up the integration in your tool, you will return to this interface to specify how to route events from your tool to services in PagerDuty.

​
Integrating With a PagerDuty Service

  1. From the Configuration menu, select Services.
  2. There are two ways to add an integration to a service:
    • If you are adding your integration to an existing service: Click the name of the service you want to add the integration to. Then, select the Integrations tab and click the New Integration button.
    • If you are creating a new service for your integration: Please read our documentation in section Configuring Services and Integrations and follow the steps outlined in the Create a New Service section, selecting Coalesce Quality as the Integration Type in step 4. Continue with the “In Coalesce Quality” section below once you have finished these steps.
  3. Enter an Integration Name in the format monitoring-tool-service-name (e.g., coalesce-quality-warehouse-one-monitoring) and select Coalesce Quality from the Integration Type menu.
  4. Click the Add Integration button to save your new integration. You will be redirected to the Integrations tab for your service.
  5. An Integration Key will be generated on this screen. Keep this key saved in a safe place, as it will be used when you configure the integration in the next section.

​
In Coalesce Quality

  1. Head to the Settings tab
  2. Click Add integration
  3. Select PagerDuty Manual
  4. Enter the following
    • Integration name: The name of your integration (default is PagerDuty)
    • Service region: Select EU or US depending on your PagerDuty service
    • Integration key: This is the Integration Key linked to your PagerDuty service integration. You can find it by opening the Integrations tab within your PagerDuty service. It’s a 32-character code.
  5. Click Create
  6. Under Settings you’ll see your new PagerDuty integration

​
Syncing the status between PagerDuty and Coalesce Quality

When taking action in PagerDuty, the following mappings apply:
  • Acknowledged: Sets the status to Investigating in Coalesce Quality
  • Resolved: Sets the status to Fixed in Coalesce Quality
An action in PagerDuty sets the status only if the issue has no status yet. When taking action in Coalesce Quality, the following mappings apply:
  • Investigating, Expected, Fixed or No action needed: acknowledges the incident in PagerDuty
  • Reset: triggers the incident again in PagerDuty
  • The issue closes, for example because the check passes again: resolves the incident in PagerDuty

​
Configuring it in Coalesce Quality

  1. Ensure that the PagerDuty integration is working by navigating to settings
  2. To set up syncing, edit the PagerDuty integration and copy the Webhook URL. You’ll need this URL to configure the Webhook in PagerDuty. When creating a new PagerDuty integration, the Webhook URL will appear after on the integration page.

​
Configuring it in PagerDuty

Follow these steps to add a webhook for Coalesce Quality:
  1. Go to Services, select the relevant service, and open the Integrations tab.
  2. Scroll to the bottom and click on the option to Add Webhooks to the service.
  3. Click New Webhook.
  4. Paste the Webhook URL you obtained earlier, and add a description (e.g., Coalesce Quality).
  5. Ensure all event subscriptions are selected.
  6. Click Add Webhook at the bottom of the page.
  7. (Optional) After the Webhook Subscription is created, PagerDuty will provide a secret to verify webhook payloads. Copy this secret and configure it in the PagerDuty service integration settings to authenticate events received through the webhook.