Project: Grafana (Observability and Analysis / Observability)
File: create-notification-policy.md

aliases: ../notifications/ # /docs/grafana/<GRAFANA_VERSION>/alerting/notifications/ ../unified-alerting/notifications/ # /docs/grafana/<GRAFANA_VERSION>/alerting/unified-alerting/notifications/ ../alerting-rules/create-notification-policy/ # /docs/grafana/<GRAFANA_VERSION>/alerting/alerting-rules/create-notification-policy/ ../manage-notifications/create-notification-policy/ # /docs/grafana/<GRAFANA_VERSION>/alerting/manage-notifications/create-notification-policy/ canonical: https://grafana.com/docs/grafana/latest/alerting/configure-notifications/create-notification-policy/ description: Configure notification policies to determine how alerts are routed to contact points keywords: grafana alerting guide notification policies routes labels: products: cloud enterprise oss title: Configure notification policies weight: 420 Notification policies determine how alerts are routed to contact points. Policies have a tree structure, where each policy can have one or more nested policies. Each policy, except for the default policy, can also match specific alert labels. Each alert is evaluated by the default policy and subsequently by each nested policy. If the Continue matching subsequent sibling nodes option is enabled for a nested policy, then evaluation continues even after one or more matches. A parent policys configuration settings and contact point information govern the behavior of an alert that does not match any of the nested policies. A default policy governs any alert that does not match a nested policy. You can configure Grafana-managed notification policies as well as notification policies for an external Alertmanager data source. For more information on notification policies, see . In the left-side menu, click Alerts & IRM and then Alerting. Click Notification policies. From the Choose Alertmanager dropdown, select an external Alertmanager. By default, the Grafana Alertmanager is selected. In the Default policy section, click ... -> Edit. In Default contact point, update the contact point to whom notifications should be sent for rules when alert rules do not match any specific policy. In Group by, choose labels to group alerts by. If multiple alerts are matched for this policy, then they are grouped by these labels. A notification is sent per group. If the field is empty (default), then all notifications are sent in a single group. Use a special label `...` to group alerts by all labels (which effectively disables grouping). In Timing options, select from the following options: Group wait Time to wait to buffer alerts of the same group before sending an initial notification. Default is 30 seconds. Group interval Minimum time interval between two notifications for a group. Default is 5 minutes. Repeat interval Minimum time interval for re-sending a notification if no new alerts were added to the group. Default is 4 hours. Click Save to save your changes. To create a new notification policy, you need to follow its tree structure. New policies created on the trunk of the tree (default policy), are the tree branches. And, subsequently, each branch can bear their own child policies. This is why you will always be adding a new nested policy under either the default policy, or under a already nested policy. In the left-side menu, click Alerts & IRM and then Alerting. Click Notification policies. From the Choose Alertmanager dropdown, select an

By default, the Grafana Alertmanager is selected. To add a top level specific policy, go to the Specific routing section (either to the default policy, or to another existing policy in which you would like to add a new nested policy) and click +New nested policy. In the Matching labels section, add one or more rules for matching alert labels. In the Contact point dropdown, select the contact point to send notification to if alert matches only this specific policy and not any of the nested policies. Optionally, enable Continue matching subsequent sibling nodes to continue matching sibling policies even after the alert matched the current policy. When this option is enabled, you can get more than one notification for one alert. Optionally, enable Override grouping to specify the same grouping as the default policy. If this option is not enabled, the default policy grouping is used. Optionally, enable Override general timings to override the timing options configured in the group notification policy. Click Save policy to save your changes. In the left-side menu, click Alerts & IRM and then Alerting. Click Notification policies. Expand the specific policy you want to update. Click + Add nested policy, then add the details using information in . Click Save policy to save your changes. In the left-side menu, click Alerts & IRM, and then Alerting. Click Notification policies. Find the policy you want to edit, then click ... -> Edit. Make any changes using instructions in . Save your changes. Grafana allows you to search within the tree of policies by the following: Label matchers Contact Points To search by contact point simply select a contact point from the Search by contact point dropdown. The policies that use that contact point will be highlighted in the user interface. To search by label matchers simply enter a valid matcher in the Search by matchers input field. Multiple matchers can be combined with a comma (`,`). An example of a valid matchers search input is: `severity=high, region=~EMEA|NASA` All matched policies will be exact matches, we currently do not support regex-style or partial matching. Mute timings are not inherited from a parent notification policy, they have to be configured in full on each level. An example of an alert configuration. Create a "default" contact point for slack notifications, and set it on the default policy. Edit the default policy grouping to group alerts by `cluster`, `namespace` and `severity` so that you get a notification per alert rule and specific kubernetes cluster and namespace. Create specific route for alerts coming from the development cluster with an appropriate contact point. Create a specific route for alerts with "critical" severity with a more invasive contact point integration, like pager duty notification. Create specific routes for particular teams that handle their own on-call rotations. {{% docs/reference %}} {{% /docs/reference %}}