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

# Dash0

> Read your agent's traces from Dash0. Coming soon.

<Note>
  **Coming soon.** Dash0 is not a trace source yet. This page describes what it will do; setup
  details are added here when it ships.
</Note>

If your agent already sends OpenTelemetry traces to [Dash0](https://www.dash0.com), Helix will read
them from there, the same way it reads [Langfuse, OpenObserve and SigNoz](/integrations/sources/otel):
Dash0 stays the place your traces live, and Helix does not keep a copy.

<CardGroup cols={2}>
  <Card title="Dash0" icon="chart-line">
    Read the traces in a Dash0 dataset for Evaluate and Diagnose.
  </Card>

  <Card title="Available now" icon="https://mintcdn.com/architech/lNudYrm3oSHgdKIT/icons/opentelemetry.svg?fit=max&auto=format&n=lNudYrm3oSHgdKIT&q=85&s=d0bd86e235ed9e1721441e2d7de905d7" href="/integrations/sources/otel" width="24" height="24" data-path="icons/opentelemetry.svg">
    Langfuse, OpenObserve and SigNoz, and local transcripts and JSONL files.
  </Card>
</CardGroup>

## How it will connect

Like the other hosted sources, a Dash0 source will be one entry under `global.sources` in
`.mutagent/config.yaml`. It will name the Dash0 endpoint and the **name** of the environment variable
that holds your Dash0 auth token, never the token itself. One source is enough: it binds to Evaluate
and Diagnose on its own.

## Until then

Export the runs you want to evaluate as JSONL and read them with a
[local JSONL source](/integrations/sources/local), or point Helix at another
[OpenTelemetry backend](/integrations/sources/otel) your agent already reports to.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.