Skip to main content

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

Langfuse

Read traces from a Langfuse project over its API.

OpenObserve

Read traces and OTel log-event streams from OpenObserve.

SigNoz

Read traces from SigNoz or any OpenTelemetry-compliant backend.
These are cloud integrations — they need the platform’s endpoint and credentials. Local transcripts and JSONL need neither; see local sources.

​
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):
.mutagent/config.yaml
otel targets an OpenTelemetry-compatible endpoint; langfuse targets a Langfuse project. See the config reference for endpoint, project, and the rest.
One source auto-binds to Evaluate and Diagnose, so a single backend is enough to run the loop on your production traces.