> ## 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.

# OpenTelemetry Sources

> Read traces from an OpenTelemetry-compatible observability platform — Langfuse, OpenObserve, SigNoz.

# OpenTelemetry trace sources

If your agent already emits traces to an **OpenTelemetry-compatible observability platform**, Helix
reads them straight from that backend — it treats the platform as the trace source and doesn't store
a copy.

<CardGroup cols={3}>
  <Card title="Langfuse" icon="https://mintcdn.com/architech/lNudYrm3oSHgdKIT/icons/langfuse.svg?fit=max&auto=format&n=lNudYrm3oSHgdKIT&q=85&s=a135050bb5d6129099f41c11b476ffc0" width="512" height="512" data-path="icons/langfuse.svg">
    Read traces from a Langfuse project over its API.
  </Card>

  <Card title="OpenObserve" icon="https://mintcdn.com/architech/lNudYrm3oSHgdKIT/icons/openobserve.svg?fit=max&auto=format&n=lNudYrm3oSHgdKIT&q=85&s=6aad749f42a01a76494390f19ac7595a" width="166" height="166" data-path="icons/openobserve.svg">
    Read traces and OTel log-event streams from OpenObserve.
  </Card>

  <Card title="SigNoz" icon="https://mintcdn.com/architech/lNudYrm3oSHgdKIT/icons/signoz.svg?fit=max&auto=format&n=lNudYrm3oSHgdKIT&q=85&s=40a5b4396310c3ba0b6bc43656e48222" width="21" height="22" data-path="icons/signoz.svg">
    Read traces from SigNoz or any OpenTelemetry-compliant backend.
  </Card>
</CardGroup>

<Note>
  These are **cloud integrations** — they need the platform's endpoint and credentials. Local
  transcripts and JSONL need neither; see [local sources](/integrations/sources/local).
</Note>

## How it connects

Declare the source in your config with the platform and a credential reference (the **name** of the
env var holding the key — never the key itself):

```yaml .mutagent/config.yaml theme={null}
global:
  sources:
    - name: prod
      platform: langfuse               # langfuse · otel
      credential_ref: LANGFUSE_SECRET_KEY
```

`otel` targets an OpenTelemetry-compatible endpoint; `langfuse` targets a Langfuse project. See the
[config reference](/helix/reference/config#globalsources) for `endpoint`, `project`, and the rest.

<Tip>
  One source auto-binds to Evaluate and Diagnose, so a single backend is enough to run the loop on
  your production traces.
</Tip>