Details
-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
-
Professional Edition
Description
Is it possible to implement "Entity Filtering" in Alert Checker configuration?
I try to explain the needs with an example, but scenarios may be also applied in other situations.
We set up an alert which checks Interface Usage on a 48-port Cisco Switch. Since it's not possible to specify single ports (we need to check usage only for 4-5 ports, instead of 24 total), we inserted "*" in Entity Match section.
What happens is that during night-time, backup process saturates one of the ports connected to backup device and a "fake" alert is generated.
A couple of solutions could be:
- possibility to specify more than an entity (for example only GigabitEthernet1/1 and GigabitEthernet1/2 ports)
- possibility to exclude (one or more) specific port in checks.
Otherwise we have to setup specific alert for specific port: it means lots of alert checkers, that may become hard to keep updated.
Regards,
Arrigo.