Alertmanager 0.23 API get silences filter

[Guillaume DESBOIS]

Hi,

In Alertmanager 0.21 the following api request works great : /api/v2/silences?filter="alertname=~Memory.*"

The filter on a label with a "like" (~) works !

But in alertmanager 0.23, the same query returns : "bad matcher format: \"alertname=~Memory.*\""

I've found that the syntax have changed and with an equal filter it's ok without the " " in the query  : /api/v2/silences?filter=alertname=MemoryHost

But if i add a ~ in the query like  /api/v2/silences?filter=alertname=~Memory.*  it returns "bad matcher format: \"alertname=~Memory.*\""

What is the syntax to get silences filter with a ~ ?

Thank you for your help

[Brian Candler]

Remove the outer double quotes for the =~ version as well.

It works for me.  For example, if I have a silence with

"matchers":[{"isEqual":true,"isRegex":true,"name":"instance","value":"r[1-8]"}, ...

then I can see it using either:

curl -g 'http://localhost:9093/api/v2/silences?filter=instance=~r[1-8]'
or

curl -g 'http://localhost:9093/api/v2/silences?filter=instance=~"r[1-8]"'

[Barry]

Since you received no replies to confirm and I'm seeing this issue myself...

removing the quotes doesn't seem to make any difference. am I wrong in thinking maybe your GET works because the silence is constructed with regex whereas silences returning "isRegex":false cannot be queried with regex?

[Brian Candler]

Please show the specific issue you're seeing: what the silence is, and what curl command line you're using to try to query it with.

Note: the "regex" attribute is not referring to the API filter, it's an attribute of the silence itself. That is, the silence uses a regex when matching alert labels to decide whether to silence them.