Project: Grafana (Observability and Analysis / Observability)
File: create-mimir-loki-managed-recording-rule.md

aliases: ../unified-alerting/alerting-rules/create-cortex-loki-managed-recording-rule/ # /docs/grafana/<GRAFANA_VERSION>/alerting/unified-alerting/alerting-rules/create-cortex-loki-managed-recording-rule/ ../unified-alerting/alerting-rules/create-mimir-loki-managed-recording-rule/ # /docs/grafana/<GRAFANA_VERSION>/alerting/unified-alerting/alerting-rules/create-mimir-loki-managed-recording-rule/ canonical: https://grafana.com/docs/grafana/latest/alerting/alerting-rules/create-mimir-loki-managed-recording-rule/ description: Create recording rules for an external Grafana Mimir or Loki instance keywords: grafana alerting guide rules recording rules configure labels: products: cloud enterprise oss title: Create recording rules weight: 300 You can create and manage recording rules for an external Grafana Mimir or Loki instance. Recording rules calculate frequently needed expressions or computationally expensive expressions in advance and save the result as a new set of time series. Querying this new time series is faster, especially for dashboards since they query the same expression every time the dashboards refresh. For more information on recording rules in Prometheus, refer to . Note: Recording rules are run as instant rules, which means that they run every 10s. To overwrite this configuration, update the min_interval in your custom configuration file. sets the minimum interval to enforce between rule evaluations. The default value is 10s which equals the scheduler interval. Rules will be adjusted if they are less than this value or if they are not multiple of the scheduler interval (10s). Higher values can help with resource management as fewer evaluations are scheduled over time. This setting has precedence over each individual rule frequency. If a rule frequency is lower than this value, then this value is enforced. Verify that you have write permission to the Prometheus or Loki data source. Otherwise, you will not be able to create or update Grafana Mimir managed alerting rules. For Grafana Mimir and Loki data sources, enable the ruler API by configuring their respective services. Loki - The `local` rule storage type, default for the Loki data source, supports only viewing of rules. To edit rules, configure one of the other rule storage types. Grafana Mimir - use the `/prometheus` prefix. The Prometheus data source supports both Grafana Mimir and Prometheus, and Grafana expects that both the and are under the same URL. You cannot provide a separate URL for the Ruler API. To create recording rules, follow these steps. Click Alerts & IRM -> Alerting -> Alert rules. Select Rule type -> Recording. Click +New recording rule. Enter recording rule name. The recording rule name must be a Prometheus metric name and contain no whitespace. Define recording rule. Select your Loki or Prometheus data source. Enter a query. Add namespace and group. From the Namespace dropdown, select an existing rule namespace or add a new one. Namespaces can contain one or more rule groups and only have an organizational purpose. From the Group dropdown, select an existing group within the selected namespace or add a new one. Newly created rules are appended to the end of the group. Rules within a group are run sequentially at a regular interval, with the same evaluation time. Add labels. Add custom labels selecting existing key-value pairs from the drop down, or add new labels by entering the new key or value . Click Save rule to save the rule or Save rule and exit to save the rule and go back to the Alerting page. {{% docs/reference %}} {{% /docs/reference %}}