> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/ai-and-agents/mcp/external/dash0.md).

# Dash0

Connect an agent to Dash0's MCP server for traces, metrics, logs and checks, using a bearer token.

Dash0 hosts an MCP server that gives an agent access to your Dash0 traces, metrics, logs and checks. ilert connects to it with a bearer token.

#### Prerequisites

* A Dash0 organisation with the MCP server enabled
* An auth token, created as described in Dash0's [Setup guide](https://www.dash0.com/hub/integrations/int_dash0_mcp/overview)
* Your Dash0 MCP **Server URL**

The endpoint depends on your Dash0 organisation, so you supply it yourself — take it from the Dash0 setup guide above.

#### Create the connector

{% stepper %}
{% step %}
Navigate to **Connectors** in the ilert navigation menu
{% endstep %}

{% step %}
Scroll to the **MCP Servers** section and click **Connect** on the **Dash0 MCP Server** card
{% endstep %}

{% step %}
Fill in the dialog:

* **Name:** a name for the connector (defaults to "Dash0 MCP")
* **Server URL:** your Dash0 MCP endpoint
* **Token:** the Dash0 auth token

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-5cc84acdd58c4be4a51336f280c7a1262ce01617%2Fdash0-mcp-create-dialog.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **Test connection** to confirm the URL and token work
{% endstep %}

{% step %}
Click **Save**
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The Server URL must be a public `https://` address — see [Host URL rules](/ai-and-agents/mcp/external.md#host-url-rules).
{% endhint %}

#### Connect MCP server with agent

To connect Dash0 with your AI SRE agent:

{% stepper %}
{% step %}
Navigate to **Agents** in the ilert navigation menu
{% endstep %}

{% step %}
Open the agent detail view for the agent you want to configure
{% endstep %}

{% step %}
Go to the **Tools** tab
{% endstep %}

{% step %}
Under the **External MCP Servers** section, locate the **Dash0 MCP Server** row
{% endstep %}

{% step %}
Click **Connect**
{% endstep %}

{% step %}
In the dialog, choose the Dash0 connector you created under **Select connector** (or create one here — the same Server URL and Token fields appear)
{% endstep %}

{% step %}
Click **Add**
{% endstep %}

{% step %}
Expand the server card to load its tools and enable the ones the agent may use, then save the agent
{% endstep %}
{% endstepper %}

The Dash0 integration is now connected and ready to use for root cause analysis.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/ai-and-agents/mcp/external/dash0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
