> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/bolt/creating-schedules/trigger-integrations/trigger-datadog-incidents.md).

# Trigger Datadog Incidents

## Datadog Integration

Connect Datadog to Paradime to automatically create incidents when Bolt runs fail, with centralized incident management and monitoring workflows.

{% hint style="info" %}
**Need to connect Datadog first?** Follow our [Datadog integration](/app-help/documentation/integrations/incident-management/datadog.md) setup guide to authenticate and connect your account.
{% endhint %}

### Configure Datadog Trigger

#### Step 1: Add Datadog Destination

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

<div data-with-frame="true"><figure><img src="/files/r51VIsidCZk8p6r5yoZ4" alt="" width="375"><figcaption></figcaption></figure></div>

#### Step 2: Set Incident Parameters

Configure the following fields to customize incidents created in Datadog:

| Field                    | Description                                | Options                                                |
| ------------------------ | ------------------------------------------ | ------------------------------------------------------ |
| **Severity**             | Priority level for the incident            | Critical, High, Medium, Low, or custom severity levels |
| **Customer Impacted**    | Whether the incident impacts customers     | Checkbox: Check if customer-facing                     |
| **State**                | Initial state of the incident              | Active, Stable, Resolved                               |
| **Commander**            | User responsible for managing the incident | Select from your Datadog users                         |
| **Notification Handles** | Additional users to notify                 | Select specific users from your Datadog account        |

#### Step 3: Confirm Configuration

1. Review your incident parameters
2. Click **Confirm** to save the trigger
3. The Datadog trigger is now active for this schedule

### What Gets Created

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

* Incident title with schedule name and workspace
* Incident details including:
  * Direct link to Paradime run logs
  * Run ID with direct link
  * Execution timestamps
  * Commands executed
  * Branch information
  * AI Summary of the command logs
* Configured severity, state, and customer impact flag
* Assigned commander and notification recipients

### Testing Your Configuration

1. Manually run a schedule that will fail
2. Check your Datadog dashboard for the new incident
3. Verify the incident contains the correct parameters and run details
4. Confirm the appropriate users were notified

### Key Benefits

* **Centralized incident management** - Track all pipeline failures alongside infrastructure incidents
* **Accelerate debugging** - Jump directly from Datadog alerts to Paradime run logs
* **Improve MTTR** - Leverage Datadog's incident workflow for faster resolution
* **Enable cross-team visibility** - Share pipeline health with platform and DevOps teams


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.paradime.io/app-help/products/bolt/creating-schedules/trigger-integrations/trigger-datadog-incidents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.