From 084a3c6b7fb99e85aa44d2269452aaaf014dfe9f Mon Sep 17 00:00:00 2001 From: Nicki de Wet Date: Fri, 19 Jan 2024 17:15:15 +0200 Subject: [PATCH] Update notifications.md (#80868) Added clarity about the order policies are evaluated --- .../fundamentals/notification-policies/notifications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/alerting/fundamentals/notification-policies/notifications.md b/docs/sources/alerting/fundamentals/notification-policies/notifications.md index fd98ef3961b..2f371905aec 100644 --- a/docs/sources/alerting/fundamentals/notification-policies/notifications.md +++ b/docs/sources/alerting/fundamentals/notification-policies/notifications.md @@ -44,7 +44,7 @@ To determine which notification policy will handle which alert instances, you ha If no policies other than the default policy are configured, the default policy will handle the alert instance. -If policies other than the default policy are defined, it will inspect those notification policies in descending order. +If policies other than the default policy are defined, it will evaluate those notification policies in the order they are displayed. If a notification policy has label matchers that match the labels of the alert instance, it will descend in to its child policies and, if there are any, will continue to look for any child policies that might have label matchers that further narrow down the set of labels, and so forth until no more child policies have been found.