OpsCanary
observabilityalertingPractitioner

Mastering Alert Rules in Grafana: A Practical Guide

5 min read Grafana DocsJun 28, 2026Reviewed for accuracy
Share
PractitionerHands-on experience recommended

Alert rules are essential for monitoring your systems effectively. They allow you to define conditions under which notifications are triggered, helping you respond to issues before they escalate. By selecting the right data and configuring the evaluation period, you can ensure that your alerts are timely and relevant.

Grafana supports two types of alert rules: Grafana-managed alert rules and data source-managed alert rules. Grafana-managed alert rules are the recommended option, as they can query backend data sources, including Prometheus-based ones, and offer a richer feature set. You can configure these rules using the + New alert rule flow in Grafana. On the other hand, data source-managed alert rules are specifically for Prometheus-based data sources like Mimir, Loki, and Prometheus, with rules stored directly in the data source. However, be cautious: pre-provisioned Loki and Prometheus data source-managed alerts have been deprecated in Grafana and cannot be created in new stacks.

In production, understanding the nuances between these alert types is crucial. Grafana-managed alerts provide flexibility and integration, while data source-managed alerts may limit your options. Always keep in mind the version notes, as the default Loki and Prometheus Grafana Cloud data sources managed by Grafana Labs may not be available for new setups. This can impact how you design your alerting strategy, so plan accordingly.

Key takeaways

  • Understand the difference between Grafana-managed and data source-managed alert rules.
  • Use the + New alert rule flow in Grafana for easy configuration.
  • Be aware that pre-provisioned data source-managed alerts are deprecated.
  • Leverage Grafana-managed alert rules for richer features and flexibility.
  • Check version compatibility for default Grafana Cloud data sources.

Why it matters

In production, timely alerts can prevent downtime and improve incident response. Properly configured alert rules ensure you catch issues early, maintaining system reliability and user satisfaction.

When NOT to use this

The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.

Want the complete reference?

Read official docs

Test what you just learned

Quiz questions written from this article

Take the quiz →
DigitalOcean Serverless InferenceSponsor

OpenAI & Anthropic-compatible inference API — no GPU provisioning needed. 55+ models, pay-per-token with no minimums. VPC + zero data retention by default.

Try Serverless Inference →

Get the daily digest

One email. 5 articles. Every morning.

No spam. Unsubscribe anytime.