> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding Dash0 as an alert source

> Turn Dash0 check rule notifications into pages and incidents in incident.io.

Dash0 is an observability platform for OpenTelemetry-native monitoring. Connect it to incident.io to page the right people when a Dash0 check fails.

When a check rule fails, Dash0 sends the alert to incident.io through its native incident.io notification channel. Check rule labels are included in the alert payload's `metadata` field, so you can use them to power [alert attributes](/alerts/attributes-and-priorities) and routing.

## Instructions

1. Head over to the [Alerts](https://app.incident.io/~/alerts/sources) section in your incident.io dashboard.

2. Select the **Sources** tab at the top of the page.

3. Press the **New alert source** button.

4. Search for **Dash0** and click **Continue** to create the alert source.

5. In Dash0, go to **Settings → Notification Channels** and add a new **incident.io** notification channel.

6. Give the channel a name, then paste in the webhook URL from the incident.io alert source setup page.

7. Under **HTTP Headers**, add an `Authorization` header set to `Bearer {secret_token}` using the token shown in incident.io.

8. Assign the channel to your check rules, either directly or using label-based routing.

9. Trigger a check or send a test notification. If it's set up correctly, the alert will appear in incident.io.

<Tip>
  You can append query parameters to the webhook URL (e.g. `?team=backend`) to route or enrich alerts without changing the check rule. They're available in attribute expressions under `query_params`.
</Tip>

Once alerts are arriving, [create an alert route](/alerts/getting-started) to filter, group, and escalate them, or to automatically create incidents.