Skip to main content
Connecting Mimir lets Traversal query your long-term metrics storage during investigations so it can detect anomalies, compare baselines, and correlate changes across services.

​
What Traversal reads

  • Metrics — time-series data via PromQL instant and range queries
  • Labels — label names and values used to scope queries to the right services and environments

​
Setup

Use this if Traversal or a Traversal Connector can reach your Mimir instance directly and you want to connect to it independently of Grafana.
1

Find your Mimir URL

Use your Mimir HTTP API endpoint. The URL should include the /prometheus path, e.g. https://mimir.yourcompany.com/prometheus.For a private or cluster-internal address, route requests through a Traversal Connector that can reach it. You can also use the Grafana proxy path.
2

Configure authentication (if required)

Mimir has no built-in authentication — credentials depend on what proxy or gateway sits in front of your Mimir instance. Traversal supports bearer token or basic auth. If your Mimir instance is unauthenticated, leave the credentials blank.
3

Note your org ID (multi-tenant only)

If your Mimir deployment uses multi-tenancy, find your tenant/org ID. Traversal sends it as the X-Scope-OrgID header on every request.
4

Configure in Traversal

Go to Company Knowledge → Integrations, select Mimir, and enter:
  • Mimir URL (including /prometheus path)
  • Credentials (optional — bearer token or basic auth if required)
  • Organization ID (optional — for multi-tenant deployments only)

​
More information