Filtering notifications and alarms
You can use filtering properties to specify how the probe filters events to receive only preferred notifications and alarms.
The NotificationFilter and ResyncFilter properties
allow you to specify what notifications and alarms are sent to the
probe. When you use these properties, specify the actual token names.
For example, the token h represents the element NV_PERCEIVED_SEVERITY.
To specify that the probe is only sent notifications with a perceived
severity of 3, set the ResyncFilter property
to $h == 3.
You can specify more complex filters
using or and and operators. For
example, to specify that the probe receives notifications with a perceived
severity of 3 or 4, set the ResyncFilter property
to the following value:
$h == 3 or $h
== 4
You can use the tokens listed below as notification filter properties.
To specify that the probe is only sent with
communications alarms, set the NotificationFilter property
to $event_name == 'x1'.
Commonly supported tokens
$type_name:
This token represents the type of notification and allows the following
possible values:
'x1': New alarm
'x3':
Alarm with its state changed to either acknowledged or unacknowledged
'x5':
Cleared alarm
$event_name: This token represents
the type of alarm and allows the following possible values:
'x1':
Communications alarm
'x2': Processing error
alarm
'x3': Environmental alarm
'x4':
Quality of service alarm
'x5': Equipment alarm
'x6':
Integrity violation
'x7': Operational violation
'x8':
Physical violation
'x9': Security service
or mechanism violation
'x10': Time domain
violation
Token supported in NotificationFilter only:
$e:
This token represents the managed object instance.
Tokens supported in ResyncFilter only
$b:
This token represents event time in units of 100 nano seconds since
October 15, 1582.
$h: This token represents
perceived severity of alarm and allows the following possible values:
2:
Critical
3: Major
4:
Minor
5: Warning