How to configure Profile Criteria and its corresponding severities?
Profile Criteria can be configured in Notification Profiles.
Usability :
The following table denotes the Profile Criteria and its dependant Severities. Use the following key to read the table.
Key:
✓ - Applicable to the corresponding criteria
✗ - Not applicable to the corresponding criteria
Note: In the "Notify only when severity is" section, alerts will only be raised when a severity is applicable to the corresponding criteria. Therefore, selecting all the severities will not necessarily return a notification unless the severity is applicable to the selected criteria.
| Criteria/Severities |
Critical |
Trouble |
Attention |
Service Down |
Clear |
| Device Misses 1/3/5 poll |
For 5 Polls
✓ |
For 3 Polls
✓ |
For 1 Poll
✓ |
✗ |
✗ |
| Hardware in problematic condition |
✓ |
✗ |
✗ |
✗ |
✗ |
| Interface or switch port has some problems (Before version 128401) |
For Interface down
✓ |
For threshold violation
✓ |
✓ |
✗ |
✗ |
| When any Interface is down (From version 128401) |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any Interface monitor has violated a threshold (From version 128401) |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any service down |
✗ |
✗ |
✗ |
✓ |
✗ |
| When any windows service down |
✗ |
✗ |
✗ |
✓ |
✗ |
| When any printer monitor down |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any UPS down |
✓ |
✗ |
✗ |
✗ |
✗ |
| When any SNMP trap received from device |
✓ |
✓ |
✓ |
✗ |
✗ |
| Threshold rule violated |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any url down |
✗ |
✗ |
✗ |
✓ |
✗ |
| When any script monitor is down or violated the threshold |
For threshold violation
✓ |
For threshold violation
✓ |
For threshold violation
✓ |
For script down
✓ |
✗ |
| When any process is down or has violated a threshold |
For threshold violation
✓ |
For process down
✓ |
✗ |
✗ |
✗ |
| When any file monitors have violated the threshold |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any folder monitors have violated the threshold |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any event log rules generates alarm |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any syslog rules generates alarm |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any exchange monitors are down |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any exchange services are down |
✗ |
✗ |
✗ |
✓ |
✗ |
| When any Active directory monitors are down |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any Active Directory services are down |
✗ |
✗ |
✗ |
✓ |
✗ |
| When any MSSQL monitors are down |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any MSSQL services are down |
✗ |
✗ |
✗ |
✓ |
✗ |
| When any virtual device has some problems |
✗ |
✗ |
✗ |
✓ |
✗ |
| When any IPSLA monitor is down |
✓ |
✗ |
✗ |
✗ |
✗ |
| When any agent is down |
✓ |
✗ |
✗ |
✗ |
✗ |
| When any UCS fault is received |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any configuration backup is failed |
✓ |
✓ |
✓ |
✓ |
✓ |
| When any configuration is changed |
✓ |
✗ |
✗ |
✗ |
✗ |
| When any NFA Alarm is triggered |
✓ |
✓ |
✓ |
✗ |
✗ |
| When any Storage Alarm is triggered |
✓ |
✓ |
✓ |
✗ |
✓ |
| When interface bandwidth exceeds its speed |
✓ |
✓ |
✓ |
✗ |
✗ |
| Notify when the alarm is cleared |
✗ |
✗ |
✗ |
✗ |
✓ |
How to get notified when an Alarm is cleared?
To get notified when an alarm is cleared, all you have to do is check the "Notify when the alarm is cleared" option in the Criteria page while configuring a notification profile. If you have already configured profiles and wish to receive alerts when an alarm is cleared, you can always edit the notification profile and select this option.
Note: You will receive an alert when an alarm is cleared, only if you have configured an alert criteria in the same notification profile.
E.g. If you have created a notification profile for the criteria "Device Misses 1/3/5 poll", you will receive an alert when the criteria matches. i.e if a device misses the specified number of polls (DEVICE DOWN). Now, you can receive an alert for DEVICE UP (DEVICE-DOWN-CLEAR) if you have checked the "Notify when the alarm is cleared" option.
