Add object_matchers example (#61235)
* Add object_matchers example * Use better terminology
This commit is contained in:
+8
-1
@@ -516,9 +516,16 @@ policies:
|
|||||||
# a very low alert volume or your upstream notification system performs
|
# a very low alert volume or your upstream notification system performs
|
||||||
# its own grouping.
|
# its own grouping.
|
||||||
group_by: ['...']
|
group_by: ['...']
|
||||||
# <list> a list of matchers that an alert has to fulfill to match the node
|
# <list> a list of prometheus-like matchers that an alert rule has to fulfill to match the node (allowed chars
|
||||||
|
# [a-zA-Z_:])
|
||||||
matchers:
|
matchers:
|
||||||
- alertname = Watchdog
|
- alertname = Watchdog
|
||||||
|
- service_id_X = serviceX
|
||||||
|
- severity =~ "warning|critical"
|
||||||
|
# <list> 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"
|
- severity =~ "warning|critical"
|
||||||
# <list> Times when the route should be muted. These must match the name of a
|
# <list> Times when the route should be muted. These must match the name of a
|
||||||
# mute time interval.
|
# mute time interval.
|
||||||
|
|||||||
Reference in New Issue
Block a user