Skip to content

Create alert in Grafana

This guide shows you how to create an alert for your application in Grafana. While we recommend creating alerts in Prometheus, Grafana can in some cases be a more user-friendly alternative.


You will need to have an application that exposes metrics. If you don't have one, you can follow the Instrument Your Application guide.

You will need some basic knowledge of PromQL to create alert conditions.

Create a new Alert rule

  1. Open Grafana and navigate to "Alerting" > "Alert rules" in the left-hand menu.
  2. Click on "+ New alert rule" button.
  3. Give your alert a descriptive name, you will choose a folder for it later.

Define query and alert condition

Define queries and/or expressions and then choose one of them as the alert rule condition. This is the threshold that an alert rule must meet or exceed in order to fire.

  1. In the "Query" section, select the data source that contains the metric you want to alert on.
  2. Write a PromQL query that returns the metric you want to alert on. For example, http_requests_total{}.
  3. In the "Expression" field, write the condition that should trigger the alert. Choose the operator and the threshold value. For example, IS ABOVE 100.

Set evaluation behavior

Define how the alert rule is evaluated.

  1. Select your team's folder in the "Folder" dropdown.
  2. Leave "Evaluation group" empty unless you want to group this alert with others.
  3. Set "Pending period" to the amount of time the alert condition must be met before the alert is triggered.

Add annotations

Add annotations to provide more context in your alert notifications.

  1. Add a summary for the alert.
  2. Add a description for the alert (optional).
  3. In the runbook URL, add a link to the runbook that describes how to resolve the alert (optional)
  4. Link a dashboard to the alert to get image snapshots in the notification (optional).
  5. Add the following custom annotations:
    • action - Describes the action that should be taken when the alert is triggered.
    • consequence - Describes the observed consequence from the user's perspective.

Configure notifications

Add custom labels to change the way your notifications are routed.

  • app - The application name.
  • env - The environment name.
  • team - The team name.
  • severity - The severity of the alert.