Alarm Filter on Dashboard - Regular expression - difference between "matches" and "is"
Article ID: 143074
NIMSOFT PROBESDX Infrastructure Management
The customer have a strange behavior with an Alarm Filter for DAshboards using the "matches" expression. They have this IP list added with pipes: 172.29.8.11 | 172.29.8.12 | 172.29.8.13 | 172.29.8.14 | 172.29.8.19 | 172.29.8.20 | 172.29.8.21 | 172.29.8.22 | 172.29.8.23
They have an alarm from an IP that does not be a part of the list above like: 172.29.8.123
But the Dashboard show this alarm and the test button brings up this alarm
The questions are:
Why, (working as designed , wrong configuration logic bug)?
Is there a better way do create this filter?
Release : 9.2.0
Component : UIM - UMP_DASHBOARD
The simple answer for this behavior is to use "is" condition
Here is the explanation:
"matches" does not mean "exact match" in this case
"is" is the correct thing to use for an exact match
In the regex matching issue, 127.29.8.12 is matching the first part of 127.29.8.123