Filtering notifications and alarms

You can specify the notifications and alarms that the probe receives from the target device using the NotificationFilter and AlarmFilter properties.

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, set the NotificationFilter property to $h == 3.

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

($h == 3) OR ($h == 4)

Token/element mappings

The following table lists the token/element mappings available for the AlarmFilter and NotificationFilter properties:
Table 1. Token/element mappings

Token

Element

a

NV_NOTIFICATION_ID

b

NV_EVENT_TIME

c

NV_SYSTEM_DN

d

NV_MANAGED_OBJECT_CLASS

e

NV_MANAGED_OBJECT_INSTANCE

f

NV_ALARM_ID

ff

NV_ALARM_LIST_ALIGNMENT_REQUIREMENT

g

NV_PROBABLE_CAUSE

gg

NV_SERVICE_USER

h

NV_PERCEIVED_SEVERITY

hh

NV_SERVICE_PROVIDER

i

NV_SPECIFIC_PROBLEM

ii

NV_SECURITY_ALARM_DETECTOR

j

NV_ADDITIONAL_TEXT

jj

NV_VENDOR_SPECIFIC_ALARM_TYPE

k

NV_ACK_TIME

l

NV_ACK_USER_ID

m

NV_ACK_SYSTEM_ID

n

NV_ACK_STATE

o

NV_COMMENTS

p

NV_BACKED_UP_STATUS

q

NV_BACK_UP_OBJECT

r

NV_THRESHOLD_INFO

s

NV_TREND_INDICATION

t

NV_STATE_CHANGE_DEFINITION

u

NV_MONITORED_ATTRIBUTES

v

NV_PROPOSED_REPAIR_ACTIONS

w

NV_CORRELATED_NOTIFICATIONS

x

NV_REASON

y

CLEAR_USER_ID

z

CLEAR_SYSTEM_ID