Configure contact point integrations on Grafana Labs

Configure the webhook notifier for Alerting

Mon, 09 Mar 2026 20:33:34 +0000

Configure the webhook notifier for Alerting

Example JSON body:

{
  "receiver": "My Super Webhook",
  "status": "firing",
  "orgId": 1,
  "alerts": [
    {
      "status": "firing",
      "labels": {
        "alertname": "High memory usage",
        "team": "blue",
        "zone": "us-1"
      },
      "annotations": {
        "description": "The system has high memory usage",
        "runbook_url": "https://myrunbook.com/runbook/1234",
        "summary": "This alert was triggered for zone us-1"
      },
      "startsAt": "2021-10-12T09:51:03.157076+02:00",
      "endsAt": "0001-01-01T00:00:00Z",
      "generatorURL": "https://play.grafana.org/alerting/1afz29v7z/edit",
      "fingerprint": "c6eadffa33fcdf37",
      "silenceURL": "https://play.grafana.org/alerting/silence/new?alertmanager=grafana&matchers=alertname%3DT2%2Cteam%3Dblue%2Czone%3Dus-1",
      "dashboardURL": "",
      "panelURL": "",
      "values": {
        "B": 44.23943737541908,
        "C": 1
      }
    },
    {
      "status": "firing",
      "labels": {
        "alertname": "High CPU usage",
        "team": "blue",
        "zone": "eu-1"
      },
      "annotations": {
        "description": "The system has high CPU usage",
        "runbook_url": "https://myrunbook.com/runbook/1234",
        "summary": "This alert was triggered for zone eu-1"
      },
      "startsAt": "2021-10-12T09:56:03.157076+02:00",
      "endsAt": "0001-01-01T00:00:00Z",
      "generatorURL": "https://play.grafana.org/alerting/d1rdpdv7k/edit",
      "fingerprint": "bc97ff14869b13e3",
      "silenceURL": "https://play.grafana.org/alerting/silence/new?alertmanager=grafana&matchers=alertname%3DT1%2Cteam%3Dblue%2Czone%3Deu-1",
      "dashboardURL": "",
      "panelURL": "",
      "values": {
        "B": 44.23943737541908,
        "C": 1
      }
    }
  ],
  "groupLabels": {},
  "commonLabels": {
    "team": "blue"
  },
  "commonAnnotations": {},
  "externalURL": "https://play.grafana.org/",
  "version": "1",
  "groupKey": "{}:{}",
  "truncatedAlerts": 0,
  "title": "[FIRING:2]  (blue)",
  "state": "alerting",
  "message": "**Firing**\n\nLabels:\n - alertname = T2\n - team = blue\n - zone = us-1\nAnnotations:\n - description = This is the alert rule checking the second system\n - runbook_url = https://myrunbook.com\n - summary = This is my summary\nSource: https://play.grafana.org/alerting/1afz29v7z/edit\nSilence: https://play.grafana.org/alerting/silence/new?alertmanager=grafana&matchers=alertname%3DT2%2Cteam%3Dblue%2Czone%3Dus-1\n\nLabels:\n - alertname = T1\n - team = blue\n - zone = eu-1\nAnnotations:\nSource: https://play.grafana.org/alerting/d1rdpdv7k/edit\nSilence: https://play.grafana.org/alerting/silence/new?alertmanager=grafana&matchers=alertname%3DT1%2Cteam%3Dblue%2Czone%3Deu-1\n"
}

Webhook fields

Body

Key	Type	Description
receiver	string	Name of the webhook
status	string	Current status of the alert, `firing` or `resolved`
orgId	number	ID of the organization related to the payload
alerts	array of alerts	Alerts that are triggering
groupLabels	object	Labels that are used for grouping, map of string keys to string values
commonLabels	object	Labels that all alarms have in common, map of string keys to string values
commonAnnotations	object	Annotations that all alarms have in common, map of string keys to string values
externalURL	string	External URL to the Grafana instance sending this webhook
version	string	Version of the payload
groupKey	string	Key that is used for grouping
truncatedAlerts	number	Number of alerts that were truncated
title	string	Will be deprecated soon
state	string	Will be deprecated soon
message	string	Will be deprecated soon

Alert

Key	Type	Description
status	string	Current status of the alert, `firing` or `resolved`
labels	object	Labels that are part of this alert, map of string keys to string values
annotations	object	Annotations that are part of this alert, map of string keys to string values
startsAt	string	Start time of the alert
endsAt	string	End time of the alert, default value when not resolved is `0001-01-01T00:00:00Z`
values	object	Values that triggered the current status
generatorURL	string	URL of the alert rule in the Grafana UI
fingerprint	string	The labels fingerprint, alarms with the same labels will have the same fingerprint
silenceURL	string	URL to silence the alert rule in the Grafana UI
dashboardURL	string	Will be deprecated soon
panelURL	string	Will be deprecated soon
imageURL	string	URL of a screenshot of a panel assigned to the rule that created this notification

Alerts are not coupled to dashboards anymore therefore the fields related to dashboards dashboardId and panelId have been removed.

WeCom

WeCom contact points need a Webhook URL. These are obtained by setting up a WeCom robot on the corresponding group chat. To obtain a Webhook URL using the WeCom desktop Client please follow these steps:

Click the “…” in the top right corner of a group chat that you want your alerts to be delivered to
Click “Add Group Robot”, select “New Robot” and give your robot a name. Click “Add Robot”
There should be a Webhook URL in the panel.

Setting	Description
Url	WeCom webhook URL.

Configure Grafana OnCall for Alerting

Mon, 09 Mar 2026 20:33:34 +0000

Configure Grafana OnCall for Alerting

Use the Grafana Alerting - Grafana OnCall integration to effortlessly connect alerts generated by Grafana Alerting with Grafana OnCall, where you can then route them according to defined escalation chains and schedules.

You can set up the integration using the Grafana Alerting application or the Grafana OnCall application. For more information on setting it up from the Grafana OnCall application, see Grafana OnCall documentation.

Before you begin

Ensure you have Installed and enabled the Grafana OnCall plugin
Ensure your version of Grafana is up-to-date and supports the new features

Procedure

To set up the Grafana OnCall integration using the Grafana Alerting application, complete the following steps.

Navigate to Alerts&IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a contact point name.
From the Integration list, select Grafana OnCall.

Note:

The Grafana OnCall integration is only available for Grafana Alertmanager.
Choose whether to add a new OnCall integration or add an existing one.
- If you add a new one, enter an Integration name.
- If you add an existing one, choose from the list of available integrations
Click Save contact point.
On the Contact points list view page, you can see the contact point with the Grafana OnCall icon.

If the integration is not yet being used anywhere in the notification policies tree, it will have Unused as its status in the Health column. It won’t receive any notifications, because there are no notifications using that integration.
Connect your contact point to a notification policy.

For more information on connecting your contact point to a notification policy, see Create notification policy.
To view your integration in the Grafana OnCall application and set up routes and escalation chains, click the Link next to the integration on the Contact points list view page in the Type column.

This redirects you to the Grafana OnCall integration page in the Grafana OnCall application. From there, you can add routes and escalation chains.

Configure Slack for Alerting

Mon, 09 Mar 2026 20:33:34 +0000

Configure Slack for Alerting

Use the Grafana Alerting - Slack integration to send Slack notifications when your alerts are firing.

There are two ways of integrating Slack into Grafana Alerting.

Use a Slack API token

Enable your app to access the Slack API. If, for example, you are interested in more granular control over permissions, or your project is expected to regularly scale, resulting in new channels being created, this is the best option.
Use a Webhook URL

Webhooks is the simpler way to post messages into Slack. Slack automatically creates a bot user with all the necessary permissions to post messages to one particular channel of your choice.

Note
Grafana Alerting only allows one Slack channel per contact point.

Before you begin

Slack API Token

If you are using a Slack API Token, complete the following steps.

Follow steps 1 and 2 of the Slack API Quickstart.
Add the chat:write.public scope to give your app the ability to post in all public channels without joining.
In OAuth Tokens for Your Workspace, copy the Bot User OAuth Token.
Open your Slack workplace.
Right click the channel you want to receive notifications in.
Click View channel details.
Scroll down and copy the Channel ID.
Note
While going through these steps, Slack may prompt you to Reinstall your app in order for the changes to take effect.

Webhook URL

If you are using a Webhook URL, follow steps 1 and 5 in the Slack API Quickstart.

Note
Make sure you copy the Slack app Webhook URL. You will need this when setting up your contact point integration in Grafana Alerting.

Procedure

To create your Slack integration in Grafana Alerting, complete the following steps.

Navigate to Alerts&IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a contact point name.
From the Integration list, select Slack.
If you are using a Slack API token:
- In the Recipient field, copy in the channel ID.
- In the Token field, copy in the Bot User OAuth Token that starts with “xoxb-”.
If you are using a Webhook URL, in the Webhook field, copy in your Slack app Webhook URL.
Click Test to check that your integration works.
Click Save contact point.

Next steps

To add the contact point and integration you created to your default notification policy, complete the following steps.

Navigate to Alerts&IRM -> Alerting -> Notification policies.
In the Default policy, click the ellipsis icon (…) and then Edit,
Change the default policy to the contact point you created.
Click Update default policy.

Note: If you have more than one contact point, add a new notification policy rather than edit the default one, so you can route specific alerts to Slack. For more information, refer to Notification policies.

Configure PagerDuty for Alerting

Mon, 09 Mar 2026 20:33:34 +0000

Configure PagerDuty for Alerting

To set up PagerDuty, provide an integration key.

Setting	Description
Integration Key	Integration key for PagerDuty
Severity	Level for dynamic notifications, default is `critical`
Custom Details	Additional 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:

{
	"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.

Configure contact point integrations on Grafana Labs

Configure the webhook notifier for Alerting

Configure the webhook notifier for Alerting

Webhook fields

Body

Alert

Removed fields related to dashboards

WeCom

Configure Grafana OnCall for Alerting

Configure Grafana OnCall for Alerting

Before you begin

Procedure

Configure Slack for Alerting

Configure Slack for Alerting

Before you begin

Slack API Token

Webhook URL

Procedure

Next steps

Configure PagerDuty for Alerting

Configure PagerDuty for Alerting