Alert Notifications

Alerting is only available in Grafana v4.0 and above.

When an alert changes state, it sends out notifications. Each alert rule can have multiple notifications. In order to add a notification to an alert rule you first need to add and configure a notification channel (can be email, PagerDuty or other integration). This is done from the Notification Channels page.

Notification Channel Setup

Alerting Notification Channels

On the Notification Channels page hit the New Channel button to go the page where you can configure and setup a new Notification Channel.

You specify a name and a type, and type specific options. You can also test the notification to make sure it’s setup correctly.

Send on all alerts

When checked, this option will nofity for all alert rules - existing and new.

Supported Notification Types

Grafana ships with the following set of notification types:

Email

To enable email notifications you have to setup SMTP settings in the Grafana config. Email notifications will upload an image of the alert graph to an external image destination if available or fallback to attaching the image to the email.

Slack

Alerting Slack Notification

To set up slack you need to configure an incoming webhook url at slack. You can follow their guide on how to do that here. If you want to include screenshots of the firing alerts in the Slack messages you have to configure either the external image destination in Grafana, or a bot integration via Slack Apps. Follow Slack’s guide to set up a bot integration and use the token provided (https://api.slack.com/bot-users), which starts with “xoxb”.

SettingDescription
Recipientallows you to override the Slack recipient.
Mentionmake it possible to include a mention in the Slack notification sent by Grafana. Ex @here or @channel
TokenIf provided, Grafana will upload the generated image via Slack’s file.upload API method, not the external image destination.

PagerDuty

To set up PagerDuty, all you have to do is to provide an API key.

SettingDescription
Integration KeyIntegration key for PagerDuty.
Auto resolve incidentsResolve incidents in PagerDuty once the alert goes back to ok

Webhook

The webhook notification is a simple way to send information about a state change over HTTP to a custom endpoint. Using this notification you could integrate Grafana into a system of your choosing.

Example json body:

{
  "title": "My alert",
  "ruleId": 1,
  "ruleName": "Load peaking!",
  "ruleUrl": "http://url.to.grafana/db/dashboard/my_dashboard?panelId=2",
  "state": "alerting",
  "imageUrl": "http://s3.image.url",
  "message": "Load is peaking. Make sure the traffic is real and spin up more webfronts",
  "evalMatches": [
    {
      "metric": "requests",
      "tags": {},
      "value": 122
    }
  ]
}
  • state - The possible values for alert state are: ok, paused, alerting, pending, no_data.

DingDing/DingTalk

Instructions in Chinese.

In DingTalk PC Client:

  1. Click “more” icon on left bottom of the panel.

  2. Click “Robot Manage” item in the pop menu, there will be a new panel call “Robot Manage”.

  3. In the “Robot Manage” panel, select “customised: customised robot with Webhook”.

  4. In the next new panel named “robot detail”, click “Add” button.

  5. In “Add Robot” panel, input a nickname for the robot and select a “message group” which the robot will join in. click “next”.

  6. There will be a Webhook URL in the panel, looks like this: https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxx. Copy this URL to the grafana Dingtalk setting page and then click “finish”.

Dingtalk supports the following “message type”: text, link and markdown. Only the text message type is supported.

Kafka

Notifications can be sent to a Kafka topic from Grafana using the Kafka REST Proxy. There are a couple of configuration options which need to be set up in Grafana UI under Kafka Settings:

  1. Kafka REST Proxy endpoint.

  2. Kafka Topic.

Once these two properties are set, you can send the alerts to Kafka for further processing or throttling.

All supported notifier

NameTypeSupport images
Slackslackyes
Pagerdutypagerdutyyes
Emailemailyes
Webhookwebhooklink
Kafkakafkano
Hipchathipchatyes
VictorOpsvictoropsyes
Sensusensuyes
OpsGenieopsgenieyes
Threemathreemayes
Pushoverpushoverno
Telegramtelegramno
Linelineno
Prometheus Alertmanagerprometheus-alertmanagerno

Enable images in notifications

Grafana can render the panel associated with the alert rule and include that in the notification. Most Notification Channels require that this image be publicly accessable (Slack and PagerDuty for example). In order to include images in alert notifications, Grafana can upload the image to an image store. It currently supports Amazon S3, Webdav, Google Cloud Storage and Azure Blob Storage. So to set that up you need to configure the external image uploader in your grafana-server ini config file.

Be aware that some notifiers requires public access to the image to be able to include it in the notification. So make sure to enable public access to the images. If your using local image uploader, your Grafana instance need to be accessible by the internet.

Currently only the Email Channels attaches images if no external image store is specified. To include images in alert notifications for other channels then you need to set up an external image store.

This is an optional requirement. You can get Slack and email notifications without setting this up.

Configure the link back to Grafana from alert notifications

All alert notifications contain a link back to the triggered alert in the Grafana instance. This url is based on the domain setting in Grafana.