This is documentation for the next version of Mimir. For the latest stable release, go to the latest version.
About Grafana Mimir dashboards and alerts requirements
Grafana Mimir dashboards and alerts require certain labels to exist on metrics scraped from Grafana Mimir. Your Prometheus or Grafana Agent must be configured to add these labels in order for the dashboards and alerts to function. The following table shows the required label names and whether they can be customized when compiling dashboards or alerts from sources.
||Yes||The Kubernetes cluster or datacenter where the Mimir cluster is running. The cluster label can be configured with the
||No||The Kubernetes namespace where the Mimir cluster is running.|
||Partially||The Kubernetes namespace and Mimir component in the format
||Yes||The unique identifier of a Mimir replica (eg. Pod ID when running on Kubernetes). The label name can be configured with the
||Yes||The unique identifier of the node or machine where the Mimir replica is running (eg. the node when running on Kubernetes). The label name can be configured with the
For rules and alerts to function properly, you must configure your Prometheus or Grafana Agent to scrape metrics from Grafana Mimir at an interval of
15s or shorter.
A metric could be exposed by multiple Grafana Mimir components, or even different applications running in the same namespace.
To provide accurate dashboards and alerts, we use the
job label to select a metric from specific components.
job is a combination of namespace and component, for example
Pre-compiled dashboards and alerts are shipped with a default configuration.
If you compile dashboards and alerts from source, you have the option to customize the regular expression used to select each Mimir component through the
job_names field in the mixin config.
job selection in monolithic mode
When running Grafana Mimir in monolithic mode and using the pre-compiled dashboards and alerts, the
job label should be set to
job selection in microservices mode
When running Grafana Mimir in microservices mode and using the pre-compiled dashboards and alerts, the
job label should be set according to the following table.
Additional resources metrics
The Grafana Mimir dashboards displaying CPU, memory, disk, and network resources utilization require Prometheus metrics scraped from the following endpoints:
For more information about the kubelet metrics and cAdvisor metrics exported by the kubelet, refer to Metrics For Kubernetes System Components.