> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traversal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mimir

> Connect Grafana Mimir for long-term Prometheus metrics storage during investigations.

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

<Tabs>
  <Tab title="Direct connection (recommended)">
    Use this if your Mimir instance is publicly accessible and you want to connect to it independently of Grafana.

    <Steps>
      <Step title="Find your Mimir URL">
        Use your Mimir HTTP API endpoint. The URL should include the `/prometheus` path, e.g. `https://mimir.yourcompany.com/prometheus`.

        <Warning>
          If your Mimir URL is a cluster-internal address (e.g. a Kubernetes service URL), it will not be reachable from Traversal. Use the Grafana proxy path instead.
        </Warning>
      </Step>

      <Step title="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.
      </Step>

      <Step title="Note your org ID (multi-tenant only)">
        If your Mimir deployment uses multi-tenant, find your tenant/org ID. Traversal sends it as the `X-Scope-OrgID` header on every request.
      </Step>

      <Step title="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)
      </Step>
    </Steps>
  </Tab>

  <Tab title="Via Grafana">
    If Mimir is configured as a datasource in your Grafana instance, Traversal can reach it through the Grafana datasource proxy. This is useful when Mimir is only accessible internally (e.g. within a cluster).

    No additional setup is needed beyond the [Grafana integration](/integrations/grafana). Traversal auto-discovers Mimir and queries it using the same Grafana service account token.

    <Note>
      Multi-tenancy is handled automatically by Grafana when going through this path. You do not need to provide an org ID in Traversal.
    </Note>
  </Tab>
</Tabs>

## More information

* [Mimir HTTP API](https://grafana.com/docs/mimir/latest/references/http-api/)