Mimir Integration

Connect Grafana Mimir with ilert to route Prometheus-based alert rules to on-call responders and improve operational visibility and response time.

Mimir is an open source, horizontally scalable, highly available, multi-tenant TSDB for long-term storage for Prometheus. The Mimir integration allows you to send Prometheus-compatible alerts, such as metric threshold breaches or anomaly detections, into ilert. These alerts are routed to on-call teams, triggering structured escalation paths to ensure timely resolution of performance and reliability issues in large-scale environments.

You can use our example prometheus setup to test the Mimir integration

In ilert

Create a Mimir alert source

1. Go to Alert sources -> Alert sources and click on Create new alert source

1. Search for Mimir in the search field, click on the Mimir tile, and click on Next.

   
2. Give your alert source a name, optionally assign teams, and click Next.
3. Select an escalation policy by creating a new one or assigning an existing one.

   
4. Select your Alert grouping preference and click Continue setup. You may click Do not group alerts for now and change it later.

   
5. The next page shows additional settings such as customer alert templates or notification prioritiy. Click on Finish setup for now.
6. On the final page, a Mimir URL will be generated that you will need later in this guide.

In Prometheus Alertmanager

In order to be able to use mimir alerts and receive notifications, you need first configure and start alertmanager

1. Install Prometheus Alertmanager in any way that suits your needs. For more information about the alertmanager installation process please visit https://prometheus.io/docs/alerting/latest/alertmanager/
2. Configure Alertmanager receivers in order to inform ilert every time there's an alert. In the example below replace the previously created Mimir URL:

alertmanager.yaml

receivers:
  - name: "ilert"
    webhook_configs:
      - url: "<your alert source url here>"
        send_resolved: true

You could also split alert to high and low priority by creating two alert sources accordingly

alertmanager.yaml

receivers:
  - name: "high-priority"
    webhook_configs:
      # high priority alert source url
      - url: "<your high priority alert source url here>"
        send_resolved: true
  - name: "low-priority"
    webhook_configs:
      # low priority alert source url
      - url: "<your low priority alert source url here>"
        send_resolved: true

In Mimir

1. Install Mimir in any way that suits your needs.
2. Configure the Mimir alert rules in order to trigger alerts regarding the rule expression. For example:

mimir-alert-rules.yaml

groups:
  - name: mimir-critical
    rules:
      - alert: MimirIngesterUnhealthy
        expr: |
          min by (cluster, namespace) (cortex_ring_members{state="Unhealthy", name="ingester"}) > 0
        for: 15m
        labels:
          severity: critical
        annotations:
          summary: Mimir cluster has unhealthy ingesters alert
          description: "Mimir cluster has unhealthy ingesters \n  VALUE = {{ $value }}\n  LABELS = {{ $labels }}"

1. Configure the Mimir ruler to send alerts to an external alertmanager and point the alert rules folder:

mimir-config.yaml

ruler:
  alertmanager_url: http://alertmanager:9093
  enable_api: true

ruler_storage:
  backend: local
  local:
    directory: /etc/alertmanager

FAQ

Will alerts in ilert be resolved automatically?

Yes, as soon as the Alertmanager sends a "RESOLVE" event, the associated alert is automatically resolved in ilert.