2.3 KiB
aliases, canonical, description, keywords, labels, title, weight, refs
| aliases | canonical | description | keywords | labels | title | weight | refs | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 alert notifications. You can assign a contact point either in the alert rule or notification policy options.
A contact point is a list of integrations, each of which sends a notification to a particular email, webhook, or service such as Slack, Pagerduty, or Grafana OnCall. Each contact point also defines the notification message to be sent, which can use the predefined message, a custom message, or notification templates.
{{< figure src="/media/docs/alerting/alerting-contact-points.png" max-width="750px" alt="Set the evaluation behavior of the alert rule in Grafana." >}}
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.