So, as you can see I have a specific routing policy for three labels up, all those labels are added in their corresponding Alerts, and Continue matching subsequent sibling nodes is enabled on this specific policy so it can move and process the nested policy, which also configured to grab alerts by a label. Nothing is coming to my teams, but If I leave the matcher empty I get all the alerts.
Hi @nessrad! Taking a look at the screenshot you provided I think the issue might have to do with duplicate matchers for the same label.
Matchers are ANDed together, meaning that all matchers must evaluate to “true” when tested against the labels on a given alert. For example, an alert with these labels:
{"alertname":"Watchdog","severity":"none"}
would NOT match this list of matchers:
matchers:
- alertname = Watchdog
- severity =~ "warning|critical"
For your specific case, this means that your route cannot be matched by an alert as the
alert would need a Pipelines label to simultaneously be equal to both “ADF” and “HUB_Pipelines”. If you’re looking for Pipelines to match either one then you want something like Pipelines=~"ADF|HUB_Pipelines"
Another misconception here is:
…Continue matching subsequent sibling nodes is enabled on this specific policy so it can move and process the nested policy…
This toggle is not necessary to continue on processing a nested policy, a nested policy will be checked regardless of this setting if the parent matched. This setting is needed to continue on to the next policy at the same depth in the tree even if the current one matched.