Trigger PagerDuty Alarms

PagerDuty Integration

Connect PagerDuty to Paradime to automatically create incidents when Bolt runs fail, with on-call escalation and automated alerting workflows.

Need to connect PagerDuty first? Follow our PagerDuty integration setup guide to authenticate and connect your account.

Configure PagerDuty Trigger

Step 1: Add PagerDuty Destination

  1. Open your Bolt Schedule

  2. Navigate to the Triggers section

  3. Click Add Destination or New destination

  4. Select PagerDuty from the dropdown

Step 2: Set Incident Parameters

Configure the following fields to customize incidents created in PagerDuty:

Field
Description
Options

From Email

Email address incidents will appear to come from

Email address associated with your PagerDuty account

Incident Type

Classification of the incident

Major Incident, or custom types from PagerDuty

Impacted Service

Service affected by the pipeline failure

Select from your configured PagerDuty services (e.g., Data Alerts)

Urgency

How quickly the incident requires attention

High, Low

Priority

Incident priority level

P1, P2, P3, P4, P5, or custom priorities

Escalation Policy

Policy for escalating the incident

Default, or custom escalation policies from PagerDuty

Select Users

Additional users to notify (optional)

Select specific users from your PagerDuty account

Step 3: Confirm Configuration

  1. Review your incident parameters

  2. Click Confirm to save the trigger

  3. The PagerDuty trigger is now active for this schedule

What Gets Created

When a Bolt run fails, PagerDuty will automatically create an incident containing:

  • Incident title with schedule and workspace details

  • Incident description including:

    • Direct link to Paradime run logs

    • Run ID and execution details

    • Start and end timestamps

    • Commands executed

    • Branch information

    • AI Summary of the command logs

  • Configured urgency, priority, and incident type

  • Automatic assignment based on escalation policy

Testing Your Configuration

  1. Manually run a schedule that will fail

  2. Check your PagerDuty dashboard for the new incident

  3. Verify the incident contains the correct parameters and run details

  4. Confirm the appropriate users were notified based on your escalation policy

Key Benefits

  • On-call escalation - Automatically page the right team members when critical pipelines fail

  • Urgency-based routing - High urgency incidents trigger immediate notifications

  • Centralized alerting - Manage data pipeline incidents alongside infrastructure alerts

  • Mobile notifications - Receive alerts on mobile devices for rapid response

Last updated

Was this helpful?