We upgraded to 0.95 this morning, and following on from #3881, we're now seeing silences not matching correctly when special chars are escaped in the regex.
Example - Top matcher is an expired alert, and bottom is a new remaking of it that's failing to match:
@heapdavid with this issue being closed this comment might be lost. If you still have .96 deployed would you mind creating another issue and linking this ?
If not I'll try to deploy and instance and write up a new issue for tracking.
@prymitive Thanks for sorting that out, we've had no problems with new or edited silences until today, a colleague uses the filtering in the top bar to create silences and that still seems to have the issue:
It also looks to be adding an extra
.* either side of the regex that we're entering, but that may be a different issue.
|Issue Title||Created Date||Updated Date|