Centralised multi-cluster metrics
A single PromQL API for every cluster and environment.
Observabilité · Courses
A complete course on Grafana Mimir: long-term storage, high availability and multi-tenancy for Prometheus metrics, from monolithic mode to a Kubernetes deployment.
LEARNING PATH
The limits of Prometheus and the components of Mimir.
Remote write, distributors, ingesters and HA deduplication.
Queries, caches, compaction and retention.
Ruler, Alertmanager and mimirtool.
Kubernetes, monitoring and troubleshooting.
Recommended practices for running the product in production.
LEARN BY DOING
A single PromQL API for every cluster and environment.
Years of metrics in object storage.
Several teams isolated by tenant, each with its own limits.
Two Prometheus servers per cluster, with no duplicates stored.
No: Prometheus (or Alloy) keeps collecting the metrics; Mimir receives them via remote_write, stores them and serves them through the same PromQL API.
Thanos is added on top of existing Prometheus servers (sidecar) and offers downsampling; Mimir centralises via remote_write and provides native multi-tenancy and limits. Both store TSDB blocks in object storage.
Not to get started: classic block storage works without it. Recent versions offer a Kafka-based ingestion architecture to decouple reads and writes at large scale.
Yes, Mimir is open source (AGPLv3). Grafana Labs also offers a managed version (Grafana Cloud Metrics) and an enterprise edition.