ec42b2a361
* Rename `Data sources` title * Relocate and rename `Introduction/Notification templates` * Rename `alert-rules/alert-instances` to `alert-rules/multi-dimensional-alerts` * Move `fundamentals/high-availability` to `setup/enable-ha` * Fix 404 high-availability alerting link on Setup HA Grafana docs * Move alert manager/contact poitns/notification templates within Notifications * Remove `Alerting on numeric data` * Restructure Introduction v2 * Continue Intro restructuring * Update docs/sources/alerting/fundamentals/alert-rules/_index.md Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> * Complete contact point TODO * Alias: alertManager * Aliases `annotation-label` + content changes * Aliases to `templating-labels-annotations` * Aliases to `queries-conditions` * Rename `rule-evaluation.md` file * Aliases: `contact points` * Aliases to `message-templating` * Aliases to `alert-rules` * Update links to new URL slugs * Remove duplicated alias * Remove trailing slash for external heading links * Remove trailing slash in heading links to other grafana pages * Change URL directory slug `fundamentals/notifications` * rename title `Configure High Availability` * Content changes * Update docs/sources/alerting/fundamentals/alert-rules/_index.md Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> * Update docs/sources/alerting/set-up/configure-alert-state-history/index.md Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> * Update docs/sources/alerting/set-up/configure-high-availability/_index.md Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> * Update docs/sources/alerting/set-up/configure-alert-state-history/index.md Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> * Update docs/sources/alerting/set-up/configure-high-availability/_index.md Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> * Update docs/sources/alerting/set-up/configure-high-availability/_index.md Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> * Update docs/sources/alerting/set-up/configure-high-availability/_index.md Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> * Update docs/sources/alerting/fundamentals/alert-rules/_index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Fix broken link reference * Fix `queries-and-conditions` * Fix `alert-rule-evaluation` ref link * Fix aliases + inline doc comments * Fix broken link --------- Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
6.8 KiB
| aliases | canonical | description | keywords | labels | title | weight | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
https://grafana.com/docs/grafana/latest/alerting/fundamentals/notifications/contact-points/ | Learn about contact points and the supported contact point integrations |
|
|
Contact points | 112 |
Contact points
Contact points contain the configuration for sending notifications. A contact point is a list of integrations, each of which sends a notification to a particular email address, service or URL. Contact points can have multiple integrations of the same kind, or a combination of integrations of different kinds. For example, a contact point could contain a Pagerduty integration; an email and Slack integration; or a Pagerduty integration, a Slack integration, and two email integrations. You can also configure a contact point with no integrations; in which case no notifications are sent.
A contact point cannot send notifications until it has been added to a notification policy. A notification policy can only send alerts to one contact point, but a contact point can be added to a number of notification policies at the same time. When an alert matches a notification policy, the alert is sent to the contact point in that notification policy, which then sends a notification to each integration in its configuration.
Contact points can be configured for the Grafana Alertmanager as well as external alertmanagers.
You can also use notification templating to customize notification messages for contact point integrations.
Note:
If you've created an OnCall contact point in the Grafana OnCall application, you can view it in the Alerting application.
Supported contact point integrations
The following table lists the contact point integrations supported by Grafana.
| Name | Type | Grafana Alertmanager | Other Alertmanagers |
|---|---|---|---|
| DingDing | dingding |
Supported | N/A |
| Discord | discord |
Supported | N/A |
email |
Supported | Supported | |
| Google Chat | googlechat |
Supported | N/A |
| Kafka | kafka |
Supported | N/A |
| Line | line |
Supported | N/A |
| Microsoft Teams | teams |
Supported | Supported |
| 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) |
| Cisco Webex Teams | webex |
Supported | Supported |
| WeCom | wecom |
Supported | N/A |
| Zenduty | webhook |
Supported | N/A |