Datasources
Datasources are the trace backends you connect to Arcane. They expose traces in OpenTelemetry format so Arcane can read and display them.
What it is
A datasource is the connection between Arcane and where your traces are stored. When you search for traces, Arcane queries the datasource you select. You can register multiple datasources—one per environment or team—and choose which one to use when searching.
Supported backends
Arcane supports four types of datasources:
- Tempo — High-scale tracing backend with TraceQL querying
- Jaeger — Mature tracing backend (Query v3 API required for OpenTelemetry traces)
- ClickHouse — Columnar database used as a trace store
- Custom API — Any backend that exposes traces in OpenTelemetry format
What you configure
When creating a datasource, you provide:
- Name and description — Help your team identify it
- Backend URL — Must be reachable from Arcane
- Source type — Tempo, Jaeger, ClickHouse, or Custom API
- Authentication — Optional credentials (Basic Auth or Bearer Token for Tempo/Jaeger)
- Custom API details — Endpoints and capabilities (if using Custom API)
Where to configure
Configure datasources in Organisation Configuration → Data Sources tab. See Data Sources for detailed setup instructions.
Related
- Data Sources — Detailed setup guide for each datasource type
- Traces — Search and view traces from your datasources