From be72e570cf7e951e593b744d29d8ffc248fed228 Mon Sep 17 00:00:00 2001 From: Alex Moreno Date: Tue, 17 Jan 2023 11:37:56 +0100 Subject: [PATCH] Fix documentation for notification policy object_matchers (#61602) * Fix documentation * Fix grammar * Update docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md Co-authored-by: George Robinson Co-authored-by: George Robinson --- .../provision-alerting-resources/file-provisioning/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md b/docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md index b3046262c9b..4719728582f 100644 --- a/docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md +++ b/docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md @@ -524,9 +524,9 @@ policies: - severity =~ "warning|critical" # a list of grafana-like matchers that an alert rule has to fulfill to match the node object_matchers: - - alertname = CPUUsage - - service_id-X = serviceX - - severity =~ "warning|critical" + - ['alertname', '=', 'CPUUsage'] + - ['service_id-X', '=', 'serviceX'] + - ['severity', '=~', 'warning|critical'] # Times when the route should be muted. These must match the name of a # mute time interval. # Additionally, the root node cannot have any mute times.