From 13cd9c3c60e7105e0e5a6da1799a8ee5aa3451a9 Mon Sep 17 00:00:00 2001 From: "Ren Goto (@ren510dev)" Date: Wed, 12 Mar 2025 16:33:15 +0900 Subject: [PATCH] Docs: Fix incorrect label groupings (#101491) fix incorrect label groupings in alerting documents Co-authored-by: Matheus Macabu --- .../fundamentals/notifications/group-alert-notifications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/alerting/fundamentals/notifications/group-alert-notifications.md b/docs/sources/alerting/fundamentals/notifications/group-alert-notifications.md index 8e2eab652e8..4434a6f9a88 100644 --- a/docs/sources/alerting/fundamentals/notifications/group-alert-notifications.md +++ b/docs/sources/alerting/fundamentals/notifications/group-alert-notifications.md @@ -55,7 +55,7 @@ Alert instances are grouped together if they have the same exact label values fo For example, given the `Group by` option set to the `team` label: - `alertname:foo, team=frontend`, and `alertname:bar, team=frontend` are in one group. -- `alertname:foo, team=backend`, and `alertname:qux, team=backend` are in another group. +- `alertname:foo, team=frontend`, and `alertname:qux, team=backend` are in another group. ### Group by alert rule or labels