Alerting docs: change icon and simplified routing (#84729)

This commit is contained in:
brendamuir 2024-03-19 21:29:45 +01:00 committed by GitHub
parent f3986f0dc7
commit d01d99a585
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 27 additions and 29 deletions

View File

@ -16,7 +16,7 @@ weight: 114
hero:
title: Grafana Alerting
level: 1
image: /media/docs/grafana-cloud/alerting-and-irm/grafana-icon-alerting.svg
image: /media/docs/alerting/alerting-bell-icon.png
width: 100
height: 100
description: Grafana Alerting allows you to learn about problems in your systems moments after they occur.

View File

@ -115,36 +115,10 @@ To do this, you need to make sure that your alert rule is in the right evaluatio
Use the guidelines in [No data and error handling](#configure-no-data-and-error-handling).
## Configure notifications
## Configure labels and notifications
{{< 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 >}}
1. Add labels to your alert rules to set which notification policy should handle your firing alert instances.
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.
1. Preview your alert instance routing set up.
Based on the labels added, alert instances are routed to the following notification policies displayed.
Expand each notification policy below to view more details.
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.
This section is for all Cloud instances and OSS instances with the alertingSimplifiedRouting feature toggle enabled.
{{< /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.
@ -186,6 +160,30 @@ Complete the following steps to set up labels and notifications.
6. Click **See details** to view alert routing details and an email preview.
## Configure notifications
{{< admonition type="note" >}}
This section is for OSS instances without the alertingSimplifiedRouting feature toggle enabled.
{{< /admonition >}}
1. Add labels to your alert rules to set which notification policy should handle your firing alert instances.
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.
2. Preview your alert instance routing set up.
Based on the labels added, alert instances are routed to the following notification policies displayed.
3. Expand each notification policy below to view more details.
4. Click **See details** to view alert routing details and an email preview.
5. Click **Save rule**.
## Add annotations
Add [annotations][annotation-label]. to provide more context on the alert in your alert notification message.