# 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.

{% hint style="info" %}
**Need to connect PagerDuty first?** Follow our [PagerDuty integration](https://docs.paradime.io/app-help/documentation/integrations/incident-management/pagerduty) setup guide to authenticate and connect your account.
{% endhint %}

### Configure PagerDuty Trigger

#### Step 1: Add PagerDuty Destination

1. Navigate to the **Triggers integration** section
2. Click **Add Integration**
3. Select **PagerDuty** from the dropdown

<div data-with-frame="true"><figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2FBfwbsiJ7Q9u6yx9vZLxG%2Fimage.png?alt=media&#x26;token=24a319d3-660b-4008-9d9c-cbdaadc6c1a1" alt="" width="375"><figcaption></figcaption></figure></div>

#### 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

<div data-with-frame="true"><figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2F6H0E45eYeG4c1PmBhwCQ%2Fimage.png?alt=media&#x26;token=5fdf46e3-8817-4ee6-935d-d6ce5567d106" alt=""><figcaption></figcaption></figure></div>

### 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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/trigger-integrations/trigger-pagerduty-alarms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.