> 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/documentation/bolt/creating-schedules/templates/incident-templates/create-datadog-incident.md).

# Create Datadog Incident

## Create Datadog Incident

Learn how to automatically create [Datadog](https://www.datadoghq.com/) incidents when dbt™ runs fail in Bolt. This integration helps data teams track and respond to pipeline failures efficiently by connecting Bolt's pipeline monitoring with Datadog's incident management system.

***

#### What You'll Get

When a run fails, Bolt automatically creates a Datadog incident containing:

* Incident title with schedule name and workspace
* Incident details including:
  * Link to Paradime run logs
  * Run ID with direct link
  * Execution timestamps
  * Commands executed
  * Branch information

***

{% hint style="success" %}
**Key Benefits for Data Teams**

* **Centralize 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
  {% endhint %}

{% hint style="warning" %}
**Prerequisites for Datadog Integration**

* Existing [Bolt schedule](https://app.paradime.io/bolt)
* Datadog account
* [Datadog API Key](https://docs.datadoghq.com/account_management/api-app-keys/)
* [Datadog Application Key](https://docs.datadoghq.com/account_management/api-app-keys/)
  {% endhint %}

***

### Setup Guide

**Step 1: Gather Your Datadog Credentials**

1. **Generate API Key**:
   * Follow the instructions in [Datadog documentation](https://docs.datadoghq.com/cloudcraft/getting-started/generate-api-key/)
   * Copy and save your API Key securely
2. **Generate Application Key**:
   * Follow the instructions in [Datadog documentation](https://docs.datadoghq.com/account_management/api-app-keys/)
   * Copy and save your Application Key securely

**Step 2: Configure Template in Bolt**

1. From the [Bolt](https://app.paradime.io/bolt) home screen, go to [Templates](https://app.paradime.io/bolt/templates)
2. Click **Incidents** and select "Create Datadog Incident"
3. Fill in the following fields:
   * **Select Schedules**: Choose the schedules for which you want to trigger this webhook. Leave blank or select all for all schedules without filtering
   * **API Key**: Enter the API Key you generated in Datadog
   * **Application Key**: Enter the Application Key you generated in Datadog
4. Click "Connect"

<figure><img src="/files/qdaC0tPvVfiFgiAxTxhT" alt=""><figcaption></figcaption></figure>

**Step 3: Test the Integration**

1. Run a Bolt schedule manually that will fail (the webhook only triggers on failed runs)
2. After the run fails, check your Datadog dashboard for the new incident
3. Verify the incident contains run failure details


---

# 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/documentation/bolt/creating-schedules/templates/incident-templates/create-datadog-incident.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.