Menu

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Enterprise Open source

Configure integrations

Configure integrations in Grafana to select your preferred communication channel for receiving notifications when your alert rules are firing. Each integration has its own configuration options and setup process. In most cases, this involves providing an API key or a Webhook URL.

Once configured, you can use integrations as part of your contact points to receive notifications whenever your alert changes its state. In this section, we’ll cover the basic steps to configure your integrations, so you can start receiving real-time alerts and stay on top of your monitoring data.

List of supported integrations

NameType
DingDingdingding
Discorddiscord
Emailemail
Google Hangouts Chatgooglechat
Hipchathipchat
Kafkakafka
Lineline
Microsoft Teamsteams
Opsgenieopsgenie
Pagerdutypagerduty
Prometheus Alertmanagerprometheus-alertmanager
Pushoverpushover
Sensusensu
Sensu Gosensugo
Slackslack
Telegramtelegram
Threemathreema
VictorOpsvictorops
Webhookwebhook

PagerDuty

To set up PagerDuty, provide an integration key.

SettingDescription
Integration KeyIntegration key for PagerDuty
SeverityLevel for dynamic notifications, default is critical
Custom DetailsAdditional details about the event

The CustomDetails field is an object containing arbitrary key-value pairs. The user-defined details are merged with the ones we use by default.

Our default values for CustomDetails are:

Go
{
	"firing":       `{{ template "__text_alert_list" .Alerts.Firing }}`,
	"resolved":     `{{ template "__text_alert_list" .Alerts.Resolved }}`,
	"num_firing":   `{{ .Alerts.Firing | len }}`,
	"num_resolved": `{{ .Alerts.Resolved | len }}`,
}

In case of duplicate keys, the user-defined details overwrite the default ones.