Filtering alarms and notifications

You can use the AlarmFilter and NotificationFilter properties to filter the events that the probe gathers from the ZTE N31 NMS.

When you use these properties, you must use the actual token names. For example, the token PERCEIVED_SEVERITY represents the element NV_PERCEIVED_SEVERITY.

To specify that the probe gathers only those notifications with a perceived severity of 3, set the NotificationFilter property to $PERCEIVED_SEVERITY == 3.

You can specify more complex filters using AND, OR, and NOT statements. For example, to specify that the probe gathers notifications with a perceived severity of 3 or 4, set the NotificationFilter property to the following value:

($PERCEIVED_SEVERITY == 3) OR ($PERCEIVED_SEVERITY == 4)

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

Table 1. Token mappings
Element	Token
`NV_NETYPE`	`NETYPE`
`NV_NEIP`	`NEIP`
`NV_EVENT_TIME`	`EVENT_TIME`
`NV_PROBABLE_CAUSE`	`PROBABLE_CAUSE`
`NV_PERCEIVED_SEVERITY`	`PERCEIVED_SEVERITY`
`NV_ENTITY_ID`	`ENTITY_ID`
`NV_ALARM_ID`	`ALARM_ID`
`NV_NOTIFICATION_ID`	`NOTIFICATION_ID`
`NV_CLEAR_USER_ID`	`CLEAR_USER_ID`
`NV_CLEAR_SYSTEM_ID`	`CLEAR_SYSTEM_ID`
`NV_ACK_USER_ID`	`ACK_USER_ID`
`NV_ACK_SYSTEM_ID`	`ACK_SYSTEM_ID`
`NV_ACK_STATE`	`ACK_STATE`
`NV_COMMENTS`	`COMMENTS`
`NV_ALARM_CLEARED_TIME`	`ALARM_CLEARED_TIME`
`NV_ALARM_CHANGED_TIME`	`ALARM_CHANGED_TIME`
`NV_ACK_TIME`	`ACK_TIME`
`NV_EVENT_CODE`	`EVENT_CODE`
`NV_EVENT_DESC`	`EVENT_DESC`
`NV_PROBABLE_CAUSE_CODE`	`PROBABLE_CAUSE_CODE`
`NV_PROBABLE_CAUSE_DESC`	`PROBABLE_CAUSE_DESC`
`NV_ADDITIONAL_INFORMATION`	`ADDITIONAL_INFORMATION`
`NV_POSITION`	`POSITION`
`NV_INFO`	`INFO`
`NV_ADDITIONAL_TEXT`	`ADDITIONAL_TEXT`