Configure contact points on Grafana Labs

Configure an Alertmanager contact point

Fri, 03 Apr 2026 19:43:06 +0000

Configure an Alertmanager contact point

Use the Alertmanager integration in a contact point to send specific alerts to a different Alertmanager.

If you have an existing Alertmanager running in your infrastructure, you can use a contact point to forward Grafana alerts to your Alertmanager.

For example, a team might run its own Alertmanager to manage notifications from other alerting systems. That team can create alerts with Grafana and configure an Alertmanager contact point to forward only their alerts to their existing Alertmanager.

This setup avoids duplicating Alertmanager configurations for better maintenance.

Note
To send all Grafana-managed alerts to an Alertmanager, add it as a data source and enable it to receive all alerts. With this setup, you can configure multiple Alertmanagers to receive all alerts.

For setup instructions, refer to Configure Alertmanagers.

Configure an Alertmanager for a contact point

To create a contact point with Alertmanager integration, complete the following steps.

Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a name for the contact point.
From the Integration list, select Alertmanager.
In the URL field, enter the URL of the Alertmanager.
(Optional) Configure optional settings.
Click Save contact point.

For more details on contact points, including how to test them and enable notifications, refer to Configure contact points.

Alertmanager settings

Option	Description
URL	The Alertmanager URL. This field is protected from modification in Grafana Cloud.

Optional settings

Option	Description
Basic Auth User	Username for HTTP Basic Authentication.
Basic Auth Password	Password for HTTP Basic Authentication.

Optional notification settings

Option	Description
Disable resolved message	Enable this option to prevent notifications when an alert resolves.

Configure Amazon SNS for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Use the Amazon SNS integration in a contact point to send alert notifications to a SNS topic. Then, configure the SNS topic to forward notifications to distinct subscriber channels used in your SNS account.

Before you begin

Before you begin, ensure you have the following:

AWS SNS Topic: An SNS topic to send notifications to.
AWS IAM Identity with necessary access: An IAM identity (e.g. user, role) with the necessary permissions to publish messages to the SNS topic.

For a minimal setup, refer to Example using an Access Key.

To create a contact point with a SNS integration, complete the following steps.

Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a name for the contact point.
From the Integration list, select AWS SNS.
Set up the required settings for your SNS configuration.
Click Save contact point.

For more details on contact points, including how to test them and enable notifications, refer to Configure contact points.

The Amazon SNS API URL: (Optional) The SNS API URL, e.g., https://sns.us-east-2.amazonaws.com. If not specified, the SNS API URL from the SNS SDK will be used.
Signature Version (sigv4): Configures AWS’s Signature Verification 4 signing process to sign requests.
- Region: (Optional) The AWS region. If blank, the region from the default credentials chain is used.
- Access Key : (Optional) The AWS API access key.
- Secret Key: (Optional) The AWS API secret key.
  
  Both Access Key and Secret Key must be provided together or left blank together.
  
  If left blank, Grafana searches for credentials using the default credentials chain, including environment variables (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY), the shared credential file, and EC2 instance roles.
- Profile: (Optional) Named AWS profile used to authenticate.
SNS topic ARN: (Optional) If you don’t specify this value, you must specify a value for the Phone number or Target ARN. If you are using a FIFO SNS topic you should set a message group interval longer than 5 minutes to prevent messages with the same group key being deduplicated by the SNS default deduplication window.
Phone number: (Optional) Phone number if message is delivered via SMS in E.164 format. If you don’t specify this value, you must specify a value for the SNS topic ARN or Target ARN.
Target ARN: (Optional) The mobile platform endpoint ARN if message is delivered via mobile notifications. If you don’t specify this value, you must specify a value for the SNS topic ARN or Phone number.
Subject: (Optional) Customize the subject. This field supports notification templates and, by default, uses the default title template (default.title). It cannot be an empty string.
Message: (Optional) Customize the message. This field supports notification templates and, by default, uses the default message template (default.message).
Attributes: (Optional) Add any SNS message attributes.

Example using an Access Key

This section outlines a minimal setup to configure Amazon SNS with Alerting.

Navigate to SNS in AWS Console:
- Go to the Amazon SNS Console.
Create a new topic:
- On the Topics page, choose “Create topic”.
- Select “Standard” as the type.
- Enter a Name for your topic, e.g., My-Topic.
- Encryption: Leave disabled for this minimal setup.
- Click “Create topic”.
(Optional) Add an email subscriber to help test:
- Within your newly created topic, click on “Create subscription”.
- Protocol: Choose Email.
- Endpoint: Enter your email address to receive test notifications.
- Click “Create subscription”.
- Confirm Subscription: Check your email and confirm the subscription by clicking the provided link.

2. Create an IAM Policy, User, and Access Key

Navigate to IAM in AWS Console:
- Go to the IAM Console.
Create a new policy:
- On the Policies page, choose “Create policy”.
- Switch to the “JSON” tab and paste the following policy, replacing Resource with your SNS topic ARN:
  JSON
```
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["sns:Publish", "sns:GetTopicAttributes"],
      "Resource": "arn:aws:sns:<region>:<account_id>:<topic_name>"
    }
  ]
}
```
- Click “Next”, name it (e.g., SNSPublishPolicy), and click “Create policy”.
Create a new IAM user and assign the policy
- In the IAM Console, on the Users page, choose “Create user”.
- Enter a User name, e.g., alerting-sns-user.
- Click “Next”.
- In Set permissions, select “Attach policies directly”.
- Search for the policy you created earlier (SNSPublishPolicy) and select it.
- Click “Next” , and click “Create user”.
Create an Access Key:
- Within your newly created user, click on “Create access key”.
- Select an appropriate use-case, e.g., Application running outside AWS.
- Click “Next” , and click “Create access key”.
- Save Credentials: Note the Access key ID and Secret access key that are required in the next step.

Follow the steps in configure Amazon SNS for a contact point, using the settings below and replacing the placeholders with the SNS and IAM values created in the previous steps.

The Amazon SNS API URL: https://sns.<region>.amazonaws.com
Signature Version (sigv4):
- Region: <region>
- Access Key: <YOUR_ACCESS_KEY>.
- Secret Key: <YOUR_SECRET_ACCESS_KEY>
SNS topic ARN: arn:aws:sns:<region>:<account_id>:<topic_name>

Test the contact point to ensure it’s working, or enable notifications for it.

Additional Resources

Configure Discord for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure Discord for Alerting

Use the Grafana Alerting - Discord integration to receive alert notifications in your Discord channels when your Grafana alert rules are triggered and resolved.

Before you begin

Create a Webhook to enable Grafana to send alert notifications to Discord channels. To create a Webhook in Discord, complete the following steps.

Follow the steps in the Intro to Webhooks guide.
Copy the Webhook URL.

Procedure

To create your Discord 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 Discord.
In the Webhook URL field, paste in your Webhook URL.
Click Test to check that your integration works.

** For Grafana Alertmanager only.**

A test alert notification should be sent to the Discord channel that you associated with the Webhook.
Click Save contact point.

Next steps

The Discord contact point is ready to receive alert notifications.

To add this contact point to your alert, complete the following steps.

In Grafana, navigate to Alerting > Alert rules.
Edit or create a new alert rule.
Scroll down to the Configure labels and notifications section.
Under Notifications click Select contact point.
From the drop-down menu, select the previously created contact point.
Click Save rule and exit.

Configure email for alert notifications

Fri, 03 Apr 2026 19:43:06 +0000

Configure email for alert notifications

Use the email integration to send alert notifications to one or more addresses.

You can customize the subject and main section of the email body. By default, the subject and body are generated from the alert data included in the notification.

Before you begin

In Grafana OSS, you must configure SMTP settings before you can enable email notifications.

Note
In Grafana Cloud, SMTP configuration is not required.

Open the configuration file. The file is typically named grafana.ini or custom.ini and located in the conf directory of your Grafana installation.
Configure the SMTP settings for your email server in the [smtp] section.
Save your changes and restart Grafana.
Test email notifications by creating a contact point.

Configure Email for a contact point

To create a contact point with a email integration, complete the following steps.

Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Create contact point.
Enter a name for the contact point.
From the Integration list, select Email.
Set up the required settings for your Email configuration.
Click Save contact point.

For more details on contact points, including how to test them and enable notifications, refer to Configure contact points.

Email settings

Option	Description
Addresses	The list of email addresses to send the notifications. Email addresses are case sensitive.

Optional settings

Option	Description
Single email	Send a single email to all email addresses rather than individual emails.

Optional settings using templates

Note
You can customize the email subject and main section of the email body, but you can’t edit HTML or CSS for visual changes.

In Grafana OSS and Enterprise, you can edit the full email template. However, this is not officially supported because it’s an internal API that may change without prior notice.

Option	Description
Subject	Sets the email subject, replacing the default template. Supports notification templates.
Message	Sets the main section of the email body, replacing the default template. Supports notification templates.

Optional notification settings

Option	Description
Disable resolved message	Enable this option to prevent notifications when an alert resolves.

Configure Google Chat for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure Google Chat for Alerting

Use the Grafana Alerting - Google Chat integration to receive alert notifications in your Google Chat space when your Grafana alert rules are triggered and resolved.

Before you begin

Create a Webhook to enable Grafana to send alert notifications to a Google Chat space. To create a Webhook in Google Chat space, complete the following steps.

Follow the steps in Google’s Chat app guide.
Copy the Webhook URL.

Procedure

To create your Google Chat 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 Google Chat.
In the URL field, paste in your Webhook URL.
Click Test to check that your integration works.

** For Grafana Alertmanager only.**

A test alert notification should be sent to the Google Chat space that you associated with the Webhook.
Click Save contact point.

Next steps

The Google Chat contact point is ready to receive alert notifications.

To add this contact point to your alert, complete the following steps.

In Grafana, navigate to Alerting > Alert rules.
Edit or create a new alert rule.
Scroll down to the Configure labels and notifications section.
Under Notifications click Select contact point.
From the drop-down menu, select the previously created contact point.
Click Save rule and exit.

Configure Grafana IRM for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure Grafana IRM for Alerting

In Grafana OSS and Grafana Enterprise, you can use a webhook contact point to send alerts to Grafana IRM. Grafana IRM can then route alerts based on escalation chains for your team’s workflows.

The alert notification flow is as follows:

^* Grafana OSS/Enterprise (send webhook alerts)->Grafana Cloud IRM (route via escalation chains)

Note
The Free Forever plan in Grafana Cloud IRM includes 3 IRM active users per month.

These instructions apply only to Grafana OSS and Grafana Enterprise. To configure IRM for Grafana Cloud Alerting, refer to the Grafana Cloud documentation.

Configure an integration in Grafana IRM

First, enable an integration in IRM to accept alerts from Grafana Alerting. You can either create a new integration or use an existing Alertmanager or Webhook integration in IRM.

To create the integration, follow the same steps as described in Configure an OnCall integration in IRM:

Navigate to Alerts & IRM -> IRM -> Integrations.
Click + New integration.
Select either Alertmanager or Webhook integration from the list.
- Alertmanager integration – Includes preconfigured IRM templates for processing Grafana and Prometheus alerts.
- Webhook integration – Uses default IRM templates for general alert processing.
Provide a title, description, and assign it to a team, then click Create Integration.
On the integration details page, copy the HTTP Endpoint URL to use in the next section.

Configure a webhook contact point in Grafana Alerting

Next, configure the contact point in Grafana Alerting to send alert notifications to Grafana IRM.

In Grafana OSS and Grafana Enterprise, you need to create a Webhook contact point using the HTTP endpoint URL you copied in the previous step.

Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a name for the contact point.
From the Integration list, select Webhook.
In the URL field, enter the HTTP endpoint URL of the IRM integration.
Click Save contact point.

After configuring the contact point in Grafana Alerting and the integration in Grafana IRM, you can start testing the Alerting-to-IRM integration.

For more information, see:

Configure contact points – Learn how to test the integration and enable notifications in Alerting.
Webhook contact point – Learn the format of the webhook payload and additional settings in Alerting.
Configure IRM alert templates – Learn how to process the incoming webhook messages in IRM.

Enable heartbeat monitoring in Grafana IRM (optional)

Enabling the heartbeat in the IRM integration acts as a monitoring for your Grafana Alerting setup. If Grafana Alerting stops sending alerts—due to downtime or misconfiguration—Grafana IRM creates a new alert group to notify you.

To set up heartbeat monitoring, you must enable the heartbeat in IRM and create an alert rule that continuously sends alerts to the heartbeat endpoint.

Enable the heartbeat for the IRM integration

In IRM, select the IRM integration you configured earlier.
Click the ⋮ (three dots) on top right, then select Heartbeat Settings.
Copy the Endpoint URL—this will be used in a new contact point in Grafana Alerting.
Set the heartbeat interval, time period after which Grafana IRM starts a new alert group if it doesn’t receive a heartbeat.

Create another Webhook contact point in Grafana Alerting

Follow the same steps as before to create a webhook contact point in Grafana Alerting:

Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a name for the contact point.
From the Integration list, select Webhook.
In the URL field, enter the endpoint URL of the heartbeat.
Click Save contact point.

You can now click the Test button to send an alert to the heartbeat endpoint. In IRM, verify the heartbeat status in the Hearbeat column on the Integrations page.

Create an alert rule in Grafana Alerting

Create a Grafana-managed alert rule with the following settings:

Always firing – Use a query and alert condition that constantly fire. For example, select a Prometheus data source and set the query to vector(1) > 0.
Configure a pending period that is shorter than the hearbeat interval.
Choose the webhook contact point you created for the heartbeat to forward alerts.
Adjust timing options in the alert rule or notification policy to ensure alerts are forwarded before the heartbeat interval elapses:
- Group wait: 0s
- Group interval: 1s
- Repeat interval: shorter than the hearbeat interval.

After it’s created, the alert rule acts as a heartbeat, verifying that Grafana Alerting is running and sending alerts to Grafana IRM.

Configure Jira for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure Jira for Alerting

Use the Jira integration in a contact point to create issues in your Jira instance when alerts fire. The integration supports both Jira Cloud and Jira Server/Data Center installations.

Before you begin

Before you begin, ensure you have the following:

A Jira instance (Cloud, Server, or Data Center)
API access credentials for Jira
Appropriate permissions to create issues in your target Jira project

Configure Jira for a contact point

To create a contact point with a Jira integration, complete the following steps:

Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a name for the contact point.
From the Integration list, select Jira.
Set up the required settings for your Jira configuration.
Click Save contact point.

For more details on contact points, including how to test them and enable notifications, refer to Configure contact points.

Required Settings

Key	Description
URL	The URL of the REST API of your Jira instance. Supported versions: `2` and `3` (e.g., `https://your-domain.atlassian.net/rest/api/3`). This field is protected from modification in Grafana Cloud.
Basic Auth User	Username for authentication. For Jira Cloud, use your email address.
Basic Auth Password	Password or personal token. For Jira Cloud, you need to obtain a personal token here and use it as the password.
API Token	An alternative to basic authentication, a bearer token is used to authorize the API requests. See Jira documentation for more information.
Project Key	The project key identifying the project where issues will be created. Project keys are unique identifiers for a project.
Issue Type	The type of issue to create (e.g., `Task`, `Bug`, `Incident`). Make sure that you specify a type that is available in your project.

Optional Settings

Key	Description
Summary	The issue title. Supports templating. Max length is 255 characters.
Description	The description of the issue. Depending on version of the API, it can be a text, Markdown, or JSON (v3 API only). Maximum size of the field is 32kb. Note: JSON is not limited by the client, and if it exceeds the size, the API is likely to reject the request.
Labels	Custom labels can be added to organize and filter issues created in Jira. Supports templating, allowing dynamic label generation based on alert data.
Priority	The priority level of the issue (e.g., `Low`, `Medium`, `High`, `Critical`). Ensure that the priority value matches the available options for your Jira instance. You can customize priority levels in Jira here.
Resolve Transition	The transition name to move the issue to a resolved state when an alert is resolved. Ensure that the value matches a valid transition available in your Jira workflow for the specified issue type. If this field is empty, the issue will not be transitioned to Done.
Reopen Transition	The transition name to move the issue back to an open state when an alert reoccurs. Ensure that the value matches a valid transition available in your Jira workflow for the specified issue type. If this field is empty, the issue will not be reopened.
Reopen Duration	The time duration (in minutes) to control whether to reopen an issue that was closed within this duration or create a new one. If not specified, the most recent issue that matches the deduplication key will be updated and reopened (if reopen transition is specified).
“Won’t fix” Transition	Specify a resolution status that should be ignored when searching for existing issues. For example, issues with this resolution will not be reopened or updated by subsequent alerts.
Deduplication Key Field	Custom field to store the deduplication key. Must be a text field. If not specified, the deduplication key is added to labels in the format of `ALERT(hash sum)`. See Jira documentation for how to create custom fields.
Fields	Allows to configure custom fields of Jira issue. The field name should be of the format like `customfield_10001`.

Configure Microsoft Teams for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure Microsoft Teams for Alerting

Use the Grafana Alerting - Microsoft Teams integration to receive notifications in your team’s channel when your alerts are firing.

Note that you can customize the title and message of the notification using notification templates; however, you cannot modify its visual appearance with adaptive cards.

Before you begin

To set up Microsoft Teams for integration with Grafana Alerting, create a new workflow that accepts Webhook requests. This allows Grafana to send alert notifications to Microsoft Teams channels.

Create a workflow in Microsoft Teams

To create a new workflow, follow the steps in Create flows in Microsoft Teams.
Microsoft provides a template library. You can use the template Post to a channel when a webhook request is received.
At the end of workflow creation wizard, copy the URL that is provided.

Note If you chose a private channel for the target of the workflow, you need to edit workflow before using it. Expand the step “Send each adaptive card”, and then expand action “Post your own adaptive card as the Flow bot to a channel”. Change “Post as” to User, and save the workflow.

Procedure

To create your MS Teams 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 Microsoft Teams.
In the URL field, copy in your Webhook URL.
Click Test to check that your integration works.

** For Grafana Alertmanager only.**

A test alert notification should be sent to the MS Team channel.
Click Save contact point.

Next steps

The Microsoft Teams contact point is ready to receive alert notifications.

To add this contact point to your alert, complete the following steps.

In Grafana, navigate to Alerting > Alert rules.
Edit or create a new alert rule.
Scroll down to the Configure labels and notifications section.
Under Notifications click Select contact point.
From the drop-down menu, select the previously created contact point.
Click Save rule and exit.

Troubleshooting

If Grafana reports that notification was sent successfully but it was not delivered to the channel, check the workflow’s run history. You can find it in the workflow details page.

Configure MQTT notifications

Fri, 03 Apr 2026 19:43:06 +0000

Configure MQTT notifications

Use the MQTT integration in contact points to send alert notifications to your MQTT broker.

Configure MQTT for a contact point

To create a contact point with MQTT integration, complete the following steps.

Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a name for the contact point.
From the Integration list, select MQTT.
Enter your broker URL in the Broker URL field. Supports tcp, ssl, mqtt, mqtts, ws, wss schemes. For example: tcp://127.0.0.1:1883.
Enter the MQTT topic name in the Topic field.
(Optional) Configure additional settings.
Click Save contact point.

For more details on contact points, including how to test them and enable notifications, refer to Configure contact points.

Required Settings

Option	Description
Broker URL	The URL of the MQTT broker. This field is protected from modification in Grafana Cloud.
Topic	The topic to which the message will be sent.

Optional Settings

Option	Description
Message format	If set to `json` (default), the notification message uses the default JSON payload. If set to `text`, the notification message is fully customizable.
Message	Depends on the Message format option. In `json` format, defines only the `message` field of the default JSON payload. In `text` format, defines the entire custom payload. This field supports notification templates.
Client ID	The client ID to use when connecting to the MQTT broker. If blank, a random client ID is used.
Username	The username to use when connecting to the MQTT broker.
Password	The password to use when connecting to the MQTT broker.
QoS	The quality of service to use when sending the message. Options are `At most once`, `At least once`, and `Exactly once`.
Retain	If set to true, the message will be retained by the broker.
TLS	TLS configuration options, including CA certificate, client certificate, and client key, and disable certificate verification.
Disable resolved message	Enable this option to prevent notifications when an alert resolves.

Default JSON payload

If the Message format option is json (the default), the payload is like this example.

{
  "receiver": "My MQTT integration",
  "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": "{}:{}",
  "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"
}

Body

If the Message format option is json (the default), the payload contains the following fields.

Key	Type	Description
`receiver`	string	Name of the contact point
`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
`message`	string	Custom message configured in Message (Optional Settings). Supports notification templates; the output is formatted as a string.

Note
When using the json Message format, only the message field of the JSON payload is customizable, and its output is formatted as a string.

To customize the full payload in text or JSON format, use the text format and define a custom payload.

Alert object

The Alert object represents an alert included in the notification group, as provided by the alerts field.

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	A link to the Grafana Dashboard if the alert has a Dashboard UID annotation.
`panelURL`	string	A link to the panel if the alert has a Panel ID annotation.
`imageURL`	string	URL of a screenshot of a panel assigned to the rule that created this notification.

Custom payload

When you set the Message format option to text, you can customize the entire payload of the MQTT message.

In this mode, the Message option defines the entire payload. It supports notification templates and can generate notification messages in plain text, JSON, or any custom format.

For examples of templates that produce plain text or JSON messages, refer to notification template examples.

Configure Opsgenie for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure Opsgenie for Alerting

Use the Grafana Alerting - Opsgenie integration to receive alert notifications in your Opsgenie alert dashboard when your Grafana alert rules are triggered and resolved.

Before you begin

Create an API key to enable Grafana to send alert notifications to Opsgenie alert dashboard.

To create an API key in Opsgenie, complete the following steps.

Follow the steps in the API integration guide.

Make sure you turn on the integration.
Copy the API key.

Procedure

To create your Opsgenie 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 Opsgenie.
In the API key field, paste in your API key.
Configure the Alert API URL.
1. For Grafana Alertmanager, enter https://api.opsgenie.com/v2/alerts.
2. For other Alertmanagers, enter the host for sending Opsgenie API requests, depending on the hosted region.
Click Test to check that your integration works.

For Grafana Alertmanager only.

A test alert notification is sent to the Alerts page in Opsgenie.
Click Save contact point.

Next steps

The Opsgenie contact point is ready to receive alert notifications.

To add this contact point to your alert rule, complete the following steps:

In Grafana, navigate to Alerting > Alert rules.
Edit or create a new alert rule.
Scroll down to the Configure labels and notifications section.
Under Notifications, click Select contact point.
From the drop-down menu, select the previously created contact point.
Click Save rule and exit.

Configure PagerDuty for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure PagerDuty for Alerting

Use the Grafana Alerting - PagerDuty integration to receive notifications in PagerDuty when your alerts are firing.

Before you begin

To set up PagerDuty for integration with Grafana Alerting, you need to create a PagerDuty account. There are several set up steps to perform within PagerDuty before you set up the integration in Grafana Alerting.

Create a Service

In PagerDuty, a service represents a component, microservice, or infrastructure element that a team oversees, manages, and monitors.

Refer to PagerDuty’s services and integrations guide.
Follow steps 1 to 5 under Create a Service.

Note
In step 5, choose Create a service without an integration.

Obtain a PagerDuty integration key

Once the service is created, click Integrations within the Service options.
Click + Add an integration.
Select Events API V2.
Click Add.
Click the drop-down arrow to display the integration details.
Copy the Integration Key.

Procedure

To create your PagerDuty 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 PagerDuty.
In the Integration Key field, copy in your integration key.
Click Test to check that your integration works.

** For Grafana Alertmanager only.**

An incident should display in the Service’s Activity tab in PagerDuty.
Click Save contact point.

Next steps

The PagerDuty contact point is ready to receive alert notifications.

To add this contact point to your alert, complete the following steps.

In Grafana, navigate to Alerting > Alert rules.
Edit or create a new alert rule.
Scroll down to the Configure labels and notifications section.
Under Notifications click Select contact point.
From the drop-down menu, select the previously created contact point.
Click Save rule and exit.

Configure Slack for Alerting

Fri, 03 Apr 2026 19:43:06 +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 that you can only setup one Slack channel per contact point.

You can customize the title and body of the Slack message using notification templates; however, you cannot modify its visual appearance with custom blocks. Additional optional settings are available to customize bot appearance, mentions, and message formatting. Refer to the Optional settings section for more details.

Before you begin

Slack API Token

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

Follow step 1 of the Slack API Quickstart to create the app.
Continue onto the second step of the Slack API Quickstart and add the chat:write.public scope as described 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 that 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, complete the following steps.

Follow the Creating an app section of the Slack API Quickstart to create the app.
Follow the Create an incoming webhook section of the Slack Incoming Webhooks guide to enable incoming webhooks for your app and create a webhook for your workspace.
Copy the Webhook URL that starts with https://hooks.slack.com/services/. You 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.

** For Grafana Alertmanager only.**
Click Save contact point.

Optional settings

You can configure additional settings to customize your Slack notifications beyond the required fields.

Customize bot appearance

You can customize how the bot appears in Slack channels:

Option	Description
Username	Override the default bot username that appears in Slack. Set the `username` field to customize the display name.
Icon emoji	Provide an emoji to use as the icon for the message. Set the `icon_emoji` field (for example, `:rocket:`). This overrides the icon URL.
Icon URL	Provide a URL to an image to use as the icon for the message. Set the `icon_url` field with the image URL.

Configure mentions

You can automatically mention users, groups, or the entire channel when notifications are sent:

Option	Description
Mention users	Mention one or more specific users in the notification. Set the `mentionUsers` field with a comma-separated list of user IDs (for example, `U024BE7LH,U024BE7LJ`). To find a user’s ID, refer to Slack’s documentation on finding member IDs.
Mention groups	Mention one or more user groups in the notification. Set the `mentionGroups` field with a comma-separated list of group IDs. You can copy group IDs from the group’s Slack profile URL.
Mention channel	Mention the entire channel or active members. Set the `mentionChannel` field to one of the following: - Empty or omit the field to disable channel mentions - `here` to mention every active channel member - `channel` to mention every channel member

Customize message content

You can customize the notification message using notification templates:

Option	Description
Title	Set a custom title for the Slack message. Use the `title` field with template variables (for example, `{{ template "slack.default.title" . }}`).
Text body	Set a custom body text for the Slack message. Use the `text` field with template variables (for example, `{{ template "slack.default.text" . }}`).
Color	Set the color of the vertical bar on the left side of the message attachment. Use the `color` field.

Advanced configuration

For specialized environments, you can override the default Slack API endpoint:

Option	Description
Endpoint URL	Specify a custom Slack API endpoint for non-webhook requests. Set the `endpointUrl` field to your custom endpoint. The default is `https://slack.com/api/chat.postMessage`.

Next steps

The Slack contact point is ready to receive alert notifications.

To add this contact point to your alert, complete the following steps.

In Grafana, navigate to Alerting > Alert rules.
Edit or create a new alert rule.
Scroll down to the Configure labels and notifications section.
Under Notifications click Select contact point.
From the drop-down menu, select the previously created contact point.
Click Save rule and exit.

Configure Telegram for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure Telegram for Alerting

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

Before you begin

Telegram limitation

Telegram messages are limited to 4096 UTF-8 characters. If you use a parse_mode other than None, truncation may result in an invalid message, causing the notification to fail. For longer messages, we recommend using an alternative contact method.

Telegram bot API token and chat ID

To integrate Grafana with Telegram, you need to get a Telegram bot API token and a chat ID (the ID of the Telegram chat where you want to receive the alert notifications). To complete the integration, use the browser version of Telegram.

Set up your Telegram bot

Create a Telegram bot. You can associate this bot to your chats and perform different actions with it, such as receiving alerts from Grafana.

To set up the bot, complete the following steps.

Open the Telegram app on your device.
Find the Telegram bot named BotFather.
Type or press /newbot.
Choose a name for the bot. It must end in bot or _bot. E.g. “my_bot”.
Copy the API token.

Chat ID

Add the bot to a group chat by following the steps below. Once the bot is added to the chat, you will be able to route your alert notifications to that group.

In the Telegram app, open a group or start a new one.
Search and add the bot to the group.
Copy the chat ID from the URL in your browser’s address bar. It should look like this: https://web.telegram.org/a/#-4266674385.

The chat ID is the sequence of numbers that follows the # symbol. For example: -4266674385.

Procedure

To create your Telegram 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 Telegram.
In the BOT API Token field, copy in the bot API token.
In the Chat ID field, copy in the chat ID.
Click Test to check that your integration works.

** For Grafana Alertmanager only.**
Click Save contact point.

Next steps

The Telegram contact point is ready to receive alert notifications.

To add this contact point to your alert, complete the following steps.

In Grafana, navigate to Alerting > Alert rules.
Edit or create a new alert rule.
Scroll down to the Configure labels and notifications section.
Under Notifications click Select contact point.
From the drop-down menu, select the previously created contact point.
Click Save rule and exit.

Configure the webhook notifier for Alerting

Fri, 03 Apr 2026 19:43:06 +0000

Configure webhook notifications

Use the webhook integration in contact points to send alert notifications to your webhook.

The webhook integration is a flexible way to integrate alerts into your system. When a notification is triggered, it sends a JSON request with alert details and additional data to the webhook endpoint.

Configure webhook for a contact point

To create a contact point with webhook integration, complete the following steps.

Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a name for the contact point.
From the Integration list, select Webhook.
In the URL field, copy in your Webhook URL.
(Optional) Configure additional settings.
Click Save contact point.

For more details on contact points, including how to test them and enable notifications, refer to Configure contact points.

Webhook settings

Option	Description
URL	The Webhook URL. This field is protected from modification in Grafana Cloud.

Optional settings

Option	Description
HTTP Method	Specifies the HTTP method to use: `POST` or `PUT`.
Basic Authentication Username	Username for HTTP Basic Authentication.
Basic Authentication Password	Password for HTTP Basic Authentication.
Authentication Header Scheme	Scheme for the `Authorization` Request Header. Default is `Bearer`.
Authentication Header Credentials	Credentials for the `Authorization` Request header.
Extra Headers	Additional HTTP headers to include in the request. You can also override the default `Content-Type: application/json` header to specify a different content type for the request payload.
Max Alerts	Maximum number of alerts to include in a notification. Any alerts exceeding this limit are ignored. `0` means no limit.
TLS	TLS configuration options, including CA certificate, client certificate, and client key.
HMAC Signature	HMAC signature configuration options.

Note
You can configure either HTTP Basic Authentication or the Authorization request header, but not both.

HMAC signature

You can secure your webhook notifications using HMAC signatures to verify the authenticity and integrity of the requests. When enabled, Grafana signs the webhook payload with a shared secret using HMAC-SHA256.

Option	Description
Secret	The shared secret key used to generate the HMAC signature.
Header	The HTTP header where the signature will be set. Default is `X-Grafana-Alerting-Signature`.
Timestamp Header	Optional header to include a timestamp in the signature calculation. When specified, Grafana will set a Unix timestamp in this header and include it in the HMAC calculation. This provides protection against replay attacks.

When HMAC signing is configured, Grafana generates a signature using HMAC-SHA256 with your secret key. If a timestamp header is specified, a Unix timestamp is included in the signature calculation. The signature is calculated as:

HMAC(timestamp + ":" + body)

The timestamp is sent in the specified header. If no timestamp header is specified, the signature is calculated just from the request body. The signature is sent as a hex-encoded string in the specified signature header.

Validate a request

To validate incoming webhook requests from Grafana, follow these steps:

Extract the signature from the header (default is X-Grafana-Alerting-Signature).
If you configured a timestamp header, extract the timestamp value and verify it’s recent to prevent replay attacks.
Calculate the expected signature:
- Create an HMAC-SHA256 hash using your shared secret
- If using timestamps, include the timestamp followed by a colon (:) before the request body
- Hash the raw request body
- Convert the result to a hexadecimal string
Compare the calculated signature with the one in the request header.

Optional settings using templates

Use the following settings to include custom data within the JSON payload. Both options support using notification templates.

Option	Description
Title	Sends the value as a string in the `title` field of the JSON payload. Supports notification templates.
Message	Sends the value as a string in the `message` field of the JSON payload. Supports notification templates.
Custom Payload	Optionally override the default payload format with a custom template.

Optional notification settings

Option	Description
Disable resolved message	Enable this option to prevent notifications when an alert resolves.

Default JSON payload

The following example shows the payload of a webhook notification containing information about two firing alerts:

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

Body

The JSON payload of webhook notifications includes the following key-value pairs:

Key	Type	Description
`receiver`	string	Name of the contact point.
`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 structure.
`groupKey`	string	Key that is used for grouping.
`truncatedAlerts`	number	Number of alerts that were truncated.
`state`	string	State of the alert group (either `alerting` or `ok`).

The following key-value pairs are also included in the JSON payload and can be configured in the webhook settings using notification templates.

Key	Type	Description
`title`	string	Custom title. Configurable in webhook settings using notification templates.
`message`	string	Custom message. Configurable in webhook settings using notification templates.

Alert

The Alert object represents an alert included in the notification group, as provided by the alerts field.

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	A link to the Grafana Dashboard if the alert has a Dashboard UID annotation.
`panelURL`	string	A link to the panel if the alert has a Panel ID annotation.
`imageURL`	string	URL of a screenshot of a panel assigned to the rule that created this notification.

Custom Payload

The Custom Payload option allows you to completely customize the webhook payload using templates. This gives you full control over the structure and content of the webhook request.

For detailed information about how to create and manage notification templates, refer to notification templates.

Note

When using Custom Payload, the Title and Message fields are ignored as the entire payload structure is determined by your template.

Custom Payload is not yet generally available in Grafana Cloud.

Option	Description
Payload Template	Notification template that defines the structure of the webhook payload.
Payload Variables	Key-value pairs that define additional variables available in the template under `.Vars.<variable_name>`.

Example of a custom payload template that includes variables:

{
  "alert_name": "{{ .CommonLabels.alertname }}",
  "status": "{{ .Status }}",
  "environment": "{{ .Vars.environment }}",
  "custom_field": "{{ .Vars.custom_field }}"
}

JSON Template Functions

When creating custom payloads, several template functions are available to help generate valid JSON structures. These include functions for creating dictionaries (coll.Dict), arrays (coll.Slice, coll.Append), and converting between JSON strings and objects (data.ToJSON, data.JSON).

For detailed information about these and other template functions, refer to notification template functions.

Example using JSON helper functions:

{- /* Generates a pretty-printed JSON payload with alert group info and individual alerts metadata. */ -}}
{{ define "webhook.custom.payload" -}}
  {{ coll.Dict
  "receiver" .Receiver
  "status" .Status
  "alerts" (tmpl.Exec "webhook.custom.simple_alerts" .Alerts | data.JSON)
  "groupLabels" .GroupLabels
  "commonLabels" .CommonLabels
  "commonAnnotations" .CommonAnnotations
  "externalURL" .ExternalURL
  "version" "1"
  "orgId"  (index .Alerts 0).OrgID
  "truncatedAlerts"  .TruncatedAlerts
  "groupKey" .GroupKey
  "state"  (tmpl.Inline "{{ if eq .Status \"resolved\" }}ok{{ else }}alerting{{ end }}" . )
  "allVariables"  .Vars
  "title" (tmpl.Exec "default.title" . )
  "message" (tmpl.Exec "default.message" . )
  | data.ToJSONPretty " "}}
{{- end }}

{{- /* Embed json templates in other json templates. */ -}}
{{ define "webhook.custom.simple_alerts" -}}
  {{- $alerts := coll.Slice -}}
  {{- range . -}}
    {{ $alerts = coll.Append (coll.Dict
    "status" .Status
    "labels" .Labels
    "startsAt" .StartsAt
    "endsAt" .EndsAt
    ) $alerts}}
  {{- end -}}
  {{- $alerts | data.ToJSON -}}
{{- end }}

Configure contact points on Grafana Labs

Configure an Alertmanager contact point

Configure an Alertmanager contact point

Configure an Alertmanager for a contact point

Alertmanager settings

Optional settings

Optional notification settings

Configure Amazon SNS for Alerting

Configure Amazon SNS notifications

Before you begin

Configure Amazon SNS for a contact point

SNS Settings

Example using an Access Key

1. Create an SNS Topic and Email Subscriber

2. Create an IAM Policy, User, and Access Key

3. Configure the SNS Contact Point in Grafana

Additional Resources

Configure Discord for Alerting

Configure Discord for Alerting

Before you begin

Procedure

Next steps

Configure email for alert notifications

Configure email for alert notifications

Before you begin

Configure Email for a contact point

Email settings

Optional settings

Optional settings using templates

Optional notification settings

Configure Google Chat for Alerting

Configure Google Chat for Alerting

Before you begin

Procedure

Next steps

Configure Grafana IRM for Alerting

Configure Grafana IRM for Alerting

Configure an integration in Grafana IRM

Configure a webhook contact point in Grafana Alerting

Enable heartbeat monitoring in Grafana IRM (optional)

Enable the heartbeat for the IRM integration

Create another Webhook contact point in Grafana Alerting

Create an alert rule in Grafana Alerting

Configure Jira for Alerting

Configure Jira for Alerting

Before you begin

Configure Jira for a contact point

Required Settings

Optional Settings

Configure Microsoft Teams for Alerting

Configure Microsoft Teams for Alerting

Before you begin

Create a workflow in Microsoft Teams

Procedure

Next steps

Troubleshooting

Configure MQTT notifications

Configure MQTT notifications

Configure MQTT for a contact point

Required Settings

Optional Settings

Default JSON payload

Body

Alert object

Custom payload

Configure Opsgenie for Alerting

Configure Opsgenie for Alerting

Before you begin

Procedure

Next steps

Configure PagerDuty for Alerting

Configure PagerDuty for Alerting

Before you begin

Create a Service

Obtain a PagerDuty integration key

Procedure

Next steps

Configure Slack for Alerting

Configure Slack for Alerting

Before you begin