mirror of
https://github.com/grafana/grafana.git
synced 2025-08-02 23:53:10 +08:00
Alerting docs: adds simplified alert routing (#82158)
* Alerting docs: adds simplified alert routing * adds to preview section * adds numbering * adds indent * deletes fullstop * ran prettier * adds feature toggle notes * fixes spelling error
This commit is contained in:
@ -123,11 +123,15 @@ To do this, you need to make sure that your alert rule is in the right evaluatio
|
||||
|
||||
## Configure notifications
|
||||
|
||||
Add labels to your alert rules to set which notification policy should handle your firing alert instances.
|
||||
{{< admonition type="note" >}}
|
||||
To try out a simplified version of routing your alerts, enable the alertingSimplifiedRouting feature toggle and refer to the following section Configure notifications (simplified).
|
||||
{{< /admonition >}}
|
||||
|
||||
All alert rules and instances, irrespective of their labels, match the default notification policy. If there are no nested policies, or no nested policies match the labels in the alert rule or alert instance, then the default notification policy is the matching policy.
|
||||
1. Add labels to your alert rules to set which notification policy should handle your firing alert instances.
|
||||
|
||||
1. Add labels if you want to change the way your notifications are routed.
|
||||
All alert rules and instances, irrespective of their labels, match the default notification policy. If there are no nested policies, or no nested policies match the labels in the alert rule or alert instance, then the default notification policy is the matching policy.
|
||||
|
||||
Add labels if you want to change the way your notifications are routed.
|
||||
|
||||
Add custom labels by selecting existing key-value pairs from the drop down, or add new labels by entering the new key or value.
|
||||
|
||||
@ -137,7 +141,56 @@ All alert rules and instances, irrespective of their labels, match the default n
|
||||
|
||||
Expand each notification policy below to view more details.
|
||||
|
||||
1. Click **See details** to view alert routing details and an email preview.
|
||||
1. Click See details to view alert routing details and an email preview.
|
||||
|
||||
1. Click **Save rule**.
|
||||
|
||||
## Configure notifications (simplified)
|
||||
|
||||
{{< admonition type="note" >}}
|
||||
To try this out, enable the alertingSimplifiedRouting feature toggle.
|
||||
|
||||
This feature is currently not available for Grafana Cloud.
|
||||
{{< /admonition >}}
|
||||
|
||||
In the **Labels** section, you can optionally choose whether to add labels to organize your alert rules, make searching easier, as well as set which notification policy should handle your firing alert instance.
|
||||
|
||||
In the **Configure notifications** section, you can choose to select a contact point directly from the alert rule form or choose to use notification policy routing as well as set up mute timings and groupings.
|
||||
|
||||
Complete the following steps to set up labels and notifications.
|
||||
|
||||
1. Add labels, if required.
|
||||
|
||||
Add custom labels by selecting existing key-value pairs from the drop down, or add new labels by entering the new key or value.
|
||||
|
||||
2. Configure who receives a notification when an alert rule fires by either choosing **Select contact point** or **Use notification policy**.
|
||||
|
||||
**Select contact point**
|
||||
|
||||
1. Choose this option to select an existing contact point.
|
||||
|
||||
All notifications for this alert rule are sent to this contact point automatically and notification policies are not used.
|
||||
|
||||
2. You can also optionally select a mute timing as well as groupings and timings to define when not to send notifications.
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
An auto-generated notification policy is generated. Only admins can view these auto-generated policies from the **Notification policies** list view. Any changes have to be made in the alert rules form. {{% /admonition %}}
|
||||
|
||||
**Use notification policy**
|
||||
|
||||
3. Choose this option to use the notification policy tree to direct your notifications.
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
All alert rules and instances, irrespective of their labels, match the default notification policy. If there are no nested policies, or no nested policies match the labels in the alert rule or alert instance, then the default notification policy is the matching policy.
|
||||
{{% /admonition %}}
|
||||
|
||||
4. Preview your alert instance routing set up.
|
||||
|
||||
Based on the labels added, alert instances are routed to the following notification policies displayed.
|
||||
|
||||
5. Expand each notification policy below to view more details.
|
||||
|
||||
6. Click **See details** to view alert routing details and an email preview.
|
||||
|
||||
## Add annotations
|
||||
|
||||
|
Reference in New Issue
Block a user