Contact points on Grafana Labs

Add contact point

Wed, 11 Mar 2026 18:13:39 +0000

Add a contact point

Use contact points to define how your contacts are notified when an alert fires.

To add a contact point

In the Grafana menu, click the Alerting (bell) icon to open the Alerting page listing existing alerts.
Click Contact points to open the page listing existing contact points.
Click New contact point.
From the Alertmanager dropdown, select an Alertmanager. By default, Grafana Alertmanager is selected.
In Name, enter a descriptive name for the contact point.
From Contact point type, select a type and fill out mandatory fields. For example, if you choose email, enter the email addresses. Or if you choose Slack, enter the Slack channel(s) and users who should be contacted.
Some contact point types, like email or webhook, have optional settings. In Optional settings, specify additional settings for the selected contact point type.
In Notification settings, optionally select Disable resolved message if you do not want to be notified when an alert resolves.
To add another contact point type, click New contact point type and repeat steps 6 through 8.
Click Save contact point to save your changes.

Edit contact point

Wed, 11 Mar 2026 18:13:39 +0000

Edit a contact point

Use contact points to define how your contacts are notified when an alert fires.

To edit a contact point

In the Alerting page, click Contact points to open the page listing existing contact points.
Find the contact point to edit, then click Edit (pen icon).
Make any changes and click Save contact point.

Test a contact point

Wed, 11 Mar 2026 18:13:39 +0000

Test a contact point

For Grafana managed contact points, you can send a test notification which helps verify a contact point is configured correctly.

To send a test notification:

In the Grafana side bar, hover your cursor over the Alerting (bell) icon and then click Contact points.
Find the contact point to test, then click Edit (pen icon). You can also create a new contact point if needed.
Click Test (paper airplane icon) to open the contact point testing modal.
Choose whether to send a predefined test notification or choose custom to add your own custom annotations and labels to include in the notification.
Click Send test notification to fire the alert.

Delete a contact point

Wed, 11 Mar 2026 18:13:39 +0000

Delete a contact point

For Grafana managed contact points, you can send a test notification which helps verify a contact point is configured correctly.

To delete a contact point

In the Alerting page, click Contact points to open the page listing existing contact points.
Find the contact point to delete, then click Delete (trash icon).
In the confirmation dialog, click Yes, delete.

Note: You cannot delete contact points that are in use by a notification policy. You will have to either delete the notification policy or update it to use another contact point.

Edit contact point

Wed, 11 Mar 2026 18:13:39 +0000

Edit Alertmanager global config

To edit global configuration options for an external Alertmanager, like SMTP server, that is used by default for all email contact types:

In the Alerting page, click Contact points to open the page listing existing contact points.
From the Alertmanager drop-down, select an external Alertmanager data source.
Click the Edit global config option.
Add global configuration settings.
Click Save global config to save your changes.

Note This option is available only for external Alertmanagers. You can configure some global options for Grafana contact types, like email settings, via Grafana configuration

List of contact point types

Wed, 11 Mar 2026 18:13:39 +0000

List of supported contact point types

The following table lists the contact point types supported by Grafana.

Name	Type	Grafana Alertmanager	Other Alertmanagers
DingDing	`dingding`	Supported	N/A
Discord	`discord`	Supported	N/A
Email	`email`	Supported	Supported
Google Hangouts	`googlechat`	Supported	N/A
Kafka	`kafka`	Supported	N/A
Line	`line`	Supported	N/A
Microsoft Teams	`teams`	Supported	N/A
Opsgenie	`opsgenie`	Supported	Supported
Pagerduty	`pagerduty`	Supported	Supported
Prometheus Alertmanager	`prometheus-alertmanager`	Supported	N/A
Pushover	`pushover`	Supported	Supported
Sensu Go	`sensugo`	Supported	N/A
Slack	`slack`	Supported	Supported
Telegram	`telegram`	Supported	N/A
Threema	`threema`	Supported	N/A
VictorOps	`victorops`	Supported	Supported
Webhook	`webhook`	Supported	Supported (different format)
WeCom	`wecom`	Supported	N/A
Zenduty	`webhook`	Supported	N/A

Message templating

Wed, 11 Mar 2026 18:13:39 +0000

Message templating

Notifications sent via contact points are built using messaging templates. Grafana’s default templates are based on the Go templating system where some fields are evaluated as text, while others are evaluated as HTML (which can affect escaping). The default template, defined in default_template.go, is a useful reference for custom templates.

Since most of the contact point fields can be templated, you can create reusable custom templates and use them in multiple contact points. The template data topic lists variables that are available for templating. The default template is defined in default_template.go which can serve as a useful reference or starting point for custom templates.

Using templates

The following example shows how to use default templates to render an alert message in Slack. The message title contains a count of alerts that are firing or were resolved. The message body lists the alerts and their status.

The following example shows the use of a custom template within one of the contact point fields.

Nested templates

You can embed templates within other templates.

For example, you can define a template fragment using the define keyword:

{{ define "mytemplate" }}
  {{ len .Alerts.Firing }} firing. {{ len .Alerts.Resolved }} resolved.
{{ end }}

You can then embed custom templates within this fragment using the template keyword. For example:

Alert summary:
{{ template "mytemplate" . }}

You can use any of the following built-in template options to embed custom templates.

Name	Notes
`default.title`	Displays high-level status information.
`default.message`	Provides a formatted summary of firing and resolved alerts.
`teams.default.message`	Similar to `default.messsage`, formatted for Microsoft Teams.

HTML in message templates

HTML in alerting message templates is escaped. We do not support rendering of HTML in the resulting notification.

Some notifiers support alternative methods of changing the look and feel of the resulting notification. For example, Grafana installs the base template for alerting emails to <grafana-install-dir>/public/emails/ng_alert_notification.html. You can edit this file to change the appearance of all alerting emails.