What Traversal reads
- Traces — distributed traces searched by tags and fetched by trace ID
Setup
Choose how Traversal will reach Tempo
- Direct Tempo endpoint
- Grafana datasource proxy
Use this option if Traversal can reach Tempo, a Tempo gateway, or Tempo query-frontend directly.If you already view traces in Grafana, start there:
- In Grafana, open Connections > Data sources.
- Select the Tempo data source you use for traces.
- Under Connection, copy the Tempo URL.
- Microservices deployments: Use the query-frontend URL or a gateway in front of Tempo.
- Monolithic deployments: Use the Tempo base URL.
- Grafana Cloud: Use your stack Tempo URL, which is typically
https://<your-stack>.grafana.net/tempo.
/api/traces/<trace_id>.Configure authentication and tenancy (if required)
Traversal can send an optional bearer token and
X-Scope-OrgID header with either option.- If you use a direct Tempo endpoint, the token usually authenticates to a Tempo gateway or reverse proxy.
- If you use a Grafana datasource proxy URL, the token must authenticate to Grafana or whatever sits in front of Grafana.
X-Scope-OrgID header. In many multi-tenant deployments, the gateway or Grafana proxy adds this header for you.Configure in Traversal
Go to Company Knowledge > Integrations, select Tempo, and enter the URL from the option you chose and any optional authentication details.Click Save.If the integration does not work as expected, confirm that you entered either a direct Tempo URL or a Grafana datasource proxy URL, not a trace-specific path, and that any required authentication or tenant headers are configured correctly.