Set up Grafana Mimir for long-term Prometheus metric storage with multi-tenancy

Steps

1. Deploy Mimir using the provided Helm chart (grafana/mimir-distributed) and configure an object storage backend (S3, GCS, or Azure Blob) in the mimir.yaml values file
2. Set the compactor, store-gateway, and ingester component replicas appropriate to your scale; start with the small.yaml reference values file from the Mimir repository
3. Configure Prometheus remote_write to send metrics to the Mimir distributor endpoint at http://mimir-distributor:8080/api/v1/push, adding an X-Scope-OrgID header for tenant isolation
4. Add a Grafana data source of type Prometheus pointing to the Mimir query-frontend endpoint and set the HTTP header X-Scope-OrgID to the tenant ID
5. Verify multi-tenant isolation by querying the same metric from two different tenants and confirming data does not bleed across tenant boundaries
6. Configure ruler storage in Mimir so that existing Prometheus alerting rules and recording rules can be managed via the Mimir ruler API (/api/v1/rules)