Multiple match clauses in alertmanager config?

Question

In the docs, it says that we can add a set of match clauses under match:. It says literally:

A set of equality matchers an alert has to fulfill to match the node.

match:
[ <labelname>: <labelvalue>, ... ]

But it doesn't tell us how to actually provide there multiple matchers. Neither does it tell us if these matchers and ANDed or ORd.

So my two questions are:

How does one properly provide multiple match clauses for a receiver?
Will these match clauses be ANDed or ORd?

I need to provide the configSecret myself, and it only seems to take the deprecated version. — Sahand, Aug 18 '21 at 10:01

score 2 · Answer 1 · answered Aug 18 '21 at 09:43

2

How does one properly provide multiple match clauses for a receiver?

I would expect following to work:

match:
  label1: value1
  lavel2: value2

Will these match clauses be ANDed or ORd?

All clauses have to match, i.e. the clauses are ANDed.

answered Aug 18 '21 at 09:43

slauth

2,667
1
10
18

score 1 · Answer 2 · edited Aug 28 '23 at 08:15

Just confirming that you can add multiple match clauses, which are ANDed. Means all clauses have to match.

Like for example:

routes:
    - matchers:
        - name: severity
          value: warning
        - name: foo
          value: bar
      receiver: slack
      repeatInterval: 24h
    - matchers:
        - name: severity
          value: warning
      receiver: msteams
      repeatInterval: 24h

In the example above, both clauses watch on the same severity but the alert message will only be send to the slack receiver, when also the label foo=bar matches. Otherwise the alert will only be send to the msteams receiver.

Multiple match clauses in alertmanager config?

2 Answers2