Filters for notifications and alarms

The NotificationFilter and AlarmFilter properties allow you to specify what notifications and alarms are sent to the probe. When you use these properties, you must use the actual token names.

For example, the token h represents the element NV_PERCEIVED_SEVERITY. So, to specify that the probe is sent only notifications with a perceived severity of 3, you must set the NotificationFilter property to $h = = 3.

You can specify more complex filters using AND and OR statements. For example, to specify that the probe is sent notifications with a perceived severity of 3 or 4, you must set the NotificationFilter property to $h = = 3 or $h = = 4.

To specify that the probe is only sent notifications for a specific managed element, set the NotificationFilter property to Managed_Node_Name~$f where $f represents the element NV_MANAGED_OBJECT_INSTANCE and Managed_Node_Name is the name of the managed object.

For example, if the set of alarms that you require return an NV_MANAGED_OBJECT_INSTANCE of SubNetwork=ONRM_RootMo, SubNetwork=SNMP, ManagedElement=SP1, set the NotificationFilter property to SP1'~$'f.
Note: The tilde character (~) is required because spaces cannot be entered in this property. For string comparisons, the first argument is considered to be contained in the second argument; which is why $f is listed second to the literal.

The following table displays the token mappings for use with the AlarmFilter and NotificationFilter properties.

Table 1. Token mappings
Element Token
NV_NOTIFICATION_ID a
NV_CORRELATED_NOTIFICATIONS b
NV_EVENT_TIME c
NV_SYSTEM_DN d
NV_MANAGED_OBJECT_CLASS e
NV_MANAGED_OBJECT_INSTANCE f
NV_PROBABLE_CAUSE g
NV_PERCEIVED_SEVERITY h
NV_SPECIFIC_PROBLEM i
NV_ADDITIONAL_TEXT j
NV_ALARM_ID k
NV_ACK_USER_ID l
NV_ACK_TIME m
NV_ACK_SYSTEM_ID n
NV_ACK_STATE o
NV_BACKED_UP_STATUS p
NV_BACK_UP_OBJECT q
NV_THRESHOLD_INFO r
NV_TREND_INDICATION s
NV_STATE_CHANGE_DEFINITION t
NV_MONITORED_ATTRIBUTES u
NV_PROPOSED_REPAIR_ACTIONS v
NV_REASON w