# Datadog

Trace monitor alerts to the release behind them. Open the **Datadog** card on the Integrations page to add a source.

## Monitor alerts

> **Beta, early access.** Flags: `datadog`, plus `forensics` or `release_health`.

Alerts become [incidents](/docs/release-health#what-broke-production) ranked against recent releases, with evidence.

1. Add a source in Bumpkit. It shows the URL and a secret.
2. In Datadog's Webhooks integration, create a webhook with the URL, a custom header `X-Bumpkit-Secret: <secret>`, and this payload:

```json
{
  "id": "$ALERT_ID",
  "event_id": "$ID",
  "title": "$EVENT_TITLE",
  "url": "$LINK",
  "transition": "$ALERT_TRANSITION",
  "date": "$DATE",
  "message": "$EVENT_MSG",
  "tags": "$TAGS"
}
```

3. Mention the webhook in a monitor's message, like `@webhook-bumpkit`.

Alerts whose transition is `Triggered`, `Re-Triggered` or `alert`, or that carry no transition, become incidents; recoveries and other transitions are ignored. Stack frames in the message (`at …(file:line)` or `File "…"` lines) are used to trace the release.

```bash
bumpkit sources add datadog --repository owner/name
bumpkit sources list datadog
```

The `sources_add` and `sources_list` MCP tools do the same. Owners and admins add sources.