Filtering 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 only sent notifications with a perceived severity of 3, you must set the NotificationFilter property to $h == 3.

You can specify multiple filters by separating each filter with a comma; for example, to specify that the probe is sent alarms with a root of 3G, a subnet of Alcatel Lucent, and a managed element of EM RNC RNCM1_421, set the AlarmFilter property to:

$e == 'Root=3G,SubNetwork=paris,SubNetwork=Alcatel-Lucent,ManagedElement=EM
RNC RNCM1_421'

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_EVENT_TIME`	`b`
`NV_SYSTEM_DN`	`c`
`NV_MANAGED_OBJECT_CLASS`	`d`
`NV_MANAGED_OBJECT_INSTANCE`	`e`
`NV_ALARM_ID`	`f`
`NV_PROBABLE_CAUSE`	`g`
`NV_PERCEIVED_SEVERITY`	`h`
`NV_SPECIFIC_PROBLEM`	`i`
`NV_ADDITIONAL_TEXT`	`j`
`NV_ACK_TIME`	`k`
`NV_ACK_USER_ID`	`l`
`NV_ACK_SYSTEM_ID`	`m`
`NV_ACK_STATE`	`n`
`NV_COMMENTS`	`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_MONITERED_ATTRIBUTES`	`u`
`NV_PROPOSED_REPAIR_ACTIONS`	`v`
`NV_CORRELATED_NOTIFICATIONS`	`w`
`NV_REASON`	`x`
`CLEAR_USER_ID`	`y`
`CLEAR_SYSTEM_ID`	`z`
`NV_ALARM_LIST_ALIGNMENT_REQUIREMENT`	`ff`
`NV_SERVICE_USER`	`gg`
`NV_SERVICE_PROVIDER`	`hh`
`NV_SECURITY_ALARM_DETECTOR`	`ii`
`NV_VENDOR_SPECIFIC_ALARM_TYPE`	`jj`