Event notification filter validation does not match execution
Description
When configuring an event notification with a filter, say:
!(IPADDR IPLIKE 10.10..)
Upon validation we are presented a list with all node IPs that are NOT 10.10.., which is correct. However, if a node within 10.10.. also has an unmonitored additional IP, that is included, notifications will be sent. Therefor the Validation display and the execution of a notification differ.
Likely the notification filter should be updated so that it uses the same query as the validation display so users are not surprised when they get erroneous notifications, hard to have the UI telling you one thing and the backend doing another.
E.g.:
Should probably include the issnmpprimary filter which I suspect the UI Validate list is using:
This query would match the validation, should be a quick fix?
When configuring an event notification with a filter, say:
!(IPADDR IPLIKE 10.10..)
Upon validation we are presented a list with all node IPs that are NOT 10.10.., which is correct. However, if a node within 10.10.. also has an unmonitored additional IP, that is included, notifications will be sent. Therefor the Validation display and the execution of a notification differ.
Likely the notification filter should be updated so that it uses the same query as the validation display so users are not surprised when they get erroneous notifications, hard to have the UI telling you one thing and the backend doing another.
E.g.:
Should probably include the issnmpprimary filter which I suspect the UI Validate list is using:
This query would match the validation, should be a quick fix?