Seems to be only one way to do it, and that's via the 'not' operator and adding all the probes to not match on.
No idea on the motivation for removing 'matching', and alternative is to add an 'OR' operator, which is something you would expect to be there regardless.
------------------------------
Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 04-13-2021 12:56 PM
From: Garin Walsh
Subject: Just stumbled across this nice tidbit related to alarm filter datasources and dashboards
From UIM 20.3.3, the matches operator is no longer available. Therefore, if you are using the matches operator in your existing dashboards, you must update the alarm filters. Otherwise, you might not get the desired output.
In prior versions of the dashboard tool, "matches" allowed you to use a regex pattern for alarm filtering.
No so anymore.
Now you are restricted to one of "is, contains, starts with, ends with".
So if you had an alarm filter that was "probe matches '/cdm|vmware/'" you have no apparent way of writing this in 20.3.3. Closest you could get is "probe contains m" but then that would also match logmon for instance.
If you know how to get around this restriction within the alarm filter structure, I'd love to know. (I know that it should be reasonable to do this in straight SQL but that has its own issues - in particular you can't have an alarm status value that propagates to a parent dashboard)
If you use matches in your dashboards and still need it, please open a support case with Broadcom and make your need known.