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.
On Monday 8 January 2024 at 14:14:07 UTC Barry wrote:
> 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?
>
> On Monday, September 27, 2021 at 12:07:21 PM UTC-4 Brian Candler wrote:
>
>> 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]";'
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/0b11932d-79db-4b68-ae20-7a942820438an%40googlegroups.com.
