Users Guide

Event Definitions | Alarms, Events, and Automation
OMNM 6.5.3 User Guide 339
Within this panel, click Add to display a popup panel through which you can select an event
definition to correlate with the one you are editing.
The following fields show on this screen:
Correlated Parent Event Definition — Displays a selector (with filter) to find the event definition
to correlate to the one that you are editing. Alarms based on the definition you select will be
correlated parents of alarms based on the definition that you are editing.
Correlated By — This is the algorithm that is used to determine if there is a correlated match
between any potential parent and child alarms. Currently the only option is Same Entity, meaning
that the two alarms must be associated with the same entity in order to be correlated in this way.
Resulting Correlation State — This indicates the type of parent/child correlation that should be
created. Caused By indicates that the parent alarm caused the child alarm to be created and
Blocked By indicates that the parent alarm is blocking progress on the child alarm. The most
significant difference in terms of how such correlations are processed occurs when the parent alarm
is cleared. In such scenarios, caused by children will be cleared automatically when the parent is
cleared, whereas blocked by children will simply be unblocked when the parent is cleared.
Priority — Indicates the priority that this entry should have in relation to the other entries in the
list. If there are multiple entries in this list, then OpenManage Network Manager will first try to
find correlated matches based on the entry with priority 1 and then if there are no matches it will
try to do so based the entry that is priority 2, and so on.
In Correlation Key Bindings, use the right/left arrows to select
Key Variables from Available
Variables
. The variables considered keys for event to alarm correlation are the key bindings for the
target alarm in the correlation process. This means that if event A is defined to include event B as a
correlated event, comparison of the key bindings defined for event B is also considered when
comparing a new alarm for event A to an existing alarm for event B.