From 3db08d4e360c2d421f197b3525af0f35c4eb09ea Mon Sep 17 00:00:00 2001 From: Alex Moreno Date: Wed, 11 Jan 2023 09:43:42 +0100 Subject: [PATCH] Add object_matchers example (#61235) * Add object_matchers example * Use better terminology --- .../file-provisioning/index.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) 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 5ae315f82b6..b3046262c9b 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 @@ -516,9 +516,16 @@ policies: # a very low alert volume or your upstream notification system performs # its own grouping. group_by: ['...'] - # a list of matchers that an alert has to fulfill to match the node + # a list of prometheus-like matchers that an alert rule has to fulfill to match the node (allowed chars + # [a-zA-Z_:]) matchers: - alertname = Watchdog + - service_id_X = serviceX + - 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" # Times when the route should be muted. These must match the name of a # mute time interval.