Docs: Refactored alert groups and silences sections (#48833)

* Initial breakdown of silences topic

* Re-organized silences

* Refactored alert groups, fixed broken relrefs and adjusted weights.

docs/sources/alerting/_index.md

@@ -32,4 +32,4 @@ Before you begin, we recommend that you familiarize yourself with some of the [f
 - [View alert groupings]({{< relref "./alert-groups.md" >}})
 - [Add or edit an alert contact point]({{< relref "./contact-points/_index.md" >}})
 - [Add or edit notification policies]({{< relref "./notifications/_index.md" >}})
-- [Add or edit silences]({{< relref "./silences.md" >}})
+- [Add or edit silences]({{< relref "./silences/_index.md" >}})

docs/sources/alerting/alert-groups/_index.md

@@ -0,0 +1,16 @@
++++
+title = "Alert groups"
+description = "Alert groups"
+keywords = ["grafana", "alerting", "alerts", "groups"]
+weight = 445
+aliases = ["/docs/grafana/latest/alerting/unified-alerting/alert-groups/"]
++++
+
+# Alert groups
+
+Alert groups show grouped alerts from an Alertmanager instance. By default, the alerts are grouped by the label keys for the root policy in [notification policies]({{< relref "../notifications/_index.md" >}}). Grouping common alerts into a single alert group prevents duplicate alerts from being fired.
+
+For more information, see:
+
+- [View alert groupings]({{< relref "./view-alert-grouping.md" >}})
+- [Filter alerts by group]({{< relref "./filter-alerts.md" >}})

docs/sources/alerting/alert-groups/filter-alerts.md

@@ -0,0 +1,21 @@
++++
+title = "Filter alerts"
+description = "Alert groups"
+keywords = ["grafana", "alerting", "alerts", "groups"]
+weight = 445
+aliases = ["/docs/grafana/latest/alerting/unified-alerting/alert-groups/"]
++++
+
+# Filter alerts by group
+
+You can use the following filters to view alerts that match specific criteria.
+
+## Search by label
+
+To use this filter option:
+
+In **Search**, enter an existing label to view alerts matching the label. For example, `environment=production,region=~US|EU,severity!=warning`.
+
+## Filter alerts by state
+
+In **States**, select from Active, Suppressed, or Unprocessed states to view alerts matching your selected state. All other alerts are hidden.

docs/sources/alerting/alert-groups/view-alert-grouping.md

@@ -6,11 +6,9 @@ title = "Alert groups"
 weight = 445
 +++
 
-# Alert groups
+# View alert groupings
 
-Alert groups show grouped alerts from an Alertmanager instance. By default, the alerts are grouped by the label keys for the root policy in [notification policies]({{< relref "./notifications/_index.md" >}}). Grouping common alerts into a single alert group prevents duplicate alerts from being fired.
-
-## View alert groupings
+To view alert groupings:
 
 1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
 1. Click **Alert grouping** to open the page listing existing groups.

docs/sources/alerting/migrating-legacy-alerts.md

@@ -15,7 +15,7 @@ Read and write access to legacy dashboard alerts and Grafana alerts are governed
 - If there are no dashboard permissions and the dashboard is under a folder, then the rule is linked to this folder and inherits its permissions.
 - If there are no dashboard permissions and the dashboard is under the General folder, then the rule is linked to the `General Alerting` folder, and the rule inherits the default permissions.
 
-> **Note:** Since there is no `Keep Last State` option for [`No Data`]({{< relref "./alerting-rules/create-grafana-managed-rule/#no-data--error-handling" >}}) in Grafana alerting, this option becomes `NoData` during the legacy rules migration. Option "Keep Last State" for [`Error handling`]({{< relref "./alerting-rules/create-grafana-managed-rule/#no-data--error-handling" >}}) is migrated to a new option `Error`. To match the behavior of the `Keep Last State`, in both cases, during the migration Grafana automatically creates a [silence]({{< relref "./silences.md" >}}) for each alert rule with a duration of 1 year.
+> **Note:** Since there is no `Keep Last State` option for [`No Data`]({{< relref "./alerting-rules/create-grafana-managed-rule/#no-data--error-handling" >}}) in Grafana alerting, this option becomes `NoData` during the legacy rules migration. Option "Keep Last State" for [`Error handling`]({{< relref "./alerting-rules/create-grafana-managed-rule/#no-data--error-handling" >}}) is migrated to a new option `Error`. To match the behavior of the `Keep Last State`, in both cases, during the migration Grafana automatically creates a [silence]({{< relref "./silences/_index.md" >}}) for each alert rule with a duration of 1 year.
 
 Notification channels are migrated to an Alertmanager configuration with the appropriate routes and receivers. Default notification channels are added as contact points to the default route. Notification channels not associated with any Dashboard alert go to the `autogen-unlinked-channel-recv` route.
 

docs/sources/alerting/silences/_index.md

@@ -0,0 +1,23 @@
++++
+title = "Silences"
+description = "Silences"
+keywords = ["grafana", "alerting", "silence", "mute"]
+weight = 450
+aliases = ["/docs/grafana/latest/alerting/unified-alerting/silences/"]
++++
+
+# About alerting silences
+
+Use silences to stop notifications from one or more alerting rules. Silences do not prevent alert rules from being evaluated. Nor do they not stop alerting instances from being shown in the user interface. Silences only stop notifications from getting created. A silence lasts for only a specified window of time.
+
+Silences do not prevent alert rules from being evaluated. They also do not stop alert instances being shown in the user interface. Silences only prevent notifications from being created.
+
+You can configure Grafana managed silences as well as silences for an [external Alertmanager data source]({{< relref "../../datasources/alertmanager.md" >}}). For more information, see [Alertmanager]({{< relref "../fundamentals/alertmanager.md" >}}).
+
+See also:
+
+- [About label matching for alert suppression]({{< relref "./label-matching-alert-suppression.md" >}})
+- [Create a silence]({{< relref "./create-silence.md" >}})
+- [Create a URL to link to a silence form]({{< relref "./linking-to-silence-form.md" >}})
+- [Edit silences]({{< relref "./edit-silence.md" >}})
+- [Remove a silences]({{< relref "./remove-silence.md" >}})

docs/sources/alerting/silences/create-silence.md

@@ -0,0 +1,22 @@
++++
+title = "Create a silence"
+description = "Add silence alert notification"
+keywords = ["grafana", "alerting", "silence", "mute"]
+weight = 450
+aliases = ["/docs/grafana/latest/alerting/unified-alerting/silences/"]
++++
+
+# Create a silence
+
+To add a silence:
+
+1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. In the Alerting page, click **Silences** to open the page listing existing contact points.
+1. From Alertmanager drop-down, select an external Alertmanager to create and manage silences for the external data source. Otherwise, keep the default option of Grafana.
+1. Click **New Silence** to open the Create silence page.
+1. In **Silence start and end**, select the start and end date to indicate when the silence should go into effect and expire.
+1. Optionally, in **Duration**, specify how long the silence is enforced. This automatically updates the end time in the **Silence start and end** field.
+1. In the **Name** and **Value** fields, enter one or more _Matching Labels_. Matchers determine which rules the silence will apply to. For more information, see [Label matching for alert suppression]({{< relref "./label-matching-alert-suppression.md" >}}).
+1. In **Comment**, add details about the silence.
+1. In **Creator**, enter the name of the silence owner or keep the default owner.
+1. Click **Create**.

docs/sources/alerting/silences/edit-silence.md

@@ -0,0 +1,14 @@
++++
+title = "Edit silences"
+description = "Edit alerting silences"
+keywords = ["grafana", "alerting", "silence", "mute"]
+weight = 450
+aliases = ["/docs/grafana/latest/alerting/unified-alerting/silences/"]
++++
+
+# Edit silences
+
+1. I In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. Click **Silences** to view the list of existing silences.
+1. Find the silence you want to edit, then click **Edit** (pen icon).
+1. Make the desired changes, then click **Submit** to save your changes.

docs/sources/alerting/silences/label-matching-alert-suppression.md

@@ -0,0 +1,21 @@
++++
+title = "Label matching and alert suppression"
+description = "Silences alert notifications"
+keywords = ["grafana", "alerting", "silence", "mute"]
+weight = 452
+aliases = ["/docs/grafana/latest/alerting/unified-alerting/silences/"]
++++
+
+# About label matching for alert suppression
+
+Grafana suppresses notifications only for alerts with labels that match all the "Matching Labels" specified in the silence.
+
+- The **Label** field is the name of the label to match. It must exactly match the label name.
+- The **Operator** field is the operator to match against the label value. The available operators are:
+
+  - `=`: Select labels that are exactly equal to the provided string.
+  - `!=`: Select labels that are not equal to the provided string.
+  - `=~`: Select labels that regex-match the provided string.
+  - `!~`: Select labels that do not regex-match the provided string.
+
+- The **Value** field matches against the corresponding value for the specified **Label** name. How it matches depends on the **Operator** value.

docs/sources/alerting/silences/linking-to-silence-form.md

@@ -0,0 +1,15 @@
++++
+title = "Create URL to link to silence form"
+description = "Linking to a silence form"
+keywords = ["grafana", "alerting", "silence", "mute"]
+weight = 451
+aliases = ["/docs/grafana/latest/alerting/unified-alerting/silences/"]
++++
+
+# Create a URL to link to a silence form
+
+When linking to a silence form, provide the default matching labels and comment via `matchers` and `comment` query parameters. The `matchers` parameter requires one more matching labels of the type `[label][operator][value]` joined by a comma while the `operator` parameter can be one of the following: `=` (equals, not regex), `!=` (not equals, not regex), `=~` (equals, regex), `!~` (not equals, regex).
+
+For example, to link to silence form with matching labels `severity=critical` & `cluster!~europe-.*` and comment `Silence critical EU alerts`, create a URL `https://mygrafana/alerting/silence/new?matchers=severity%3Dcritical%2Ccluster!~europe-*&comment=Silence%20critical%20EU%20alert`.
+
+To link to a new silence page for an [external Alertmanager]({{< relref "../../datasources/alertmanager.md" >}}), add a `alertmanager` query parameter with the Alertmanager data source name.

docs/sources/alerting/silences/remove-silence.md

@@ -0,0 +1,15 @@
++++
+title = "Remove silences"
+description = "Remove alerting silences"
+keywords = ["grafana", "alerting", "silence", "mute"]
+weight = 451
+aliases = ["/docs/grafana/latest/alerting/unified-alerting/silences/"]
++++
+
+# Remove silences
+
+1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. Click **Silences** to view the list of existing silences.
+1. Select the silence you want to end, then click **Unsilence**.
+
+> **Note:** You cannot remove a silence manually. Silences that have ended are retained and listed for five days.