Users Guide

Understanding Performance Monitoring | Performance Monitoring
OMNM 6.5.3 User Guide 367
28 Is one of these
conditions met? State
change, always emit,
re-emit timeout
Are any of these conditions met?
• The state changed with the last polling attempt. Either the device was
previously available/reachable and now it is notavailable or notreachable or
vice versa. If the state is the same as before (for example, it was unavailable
and this is still the case) then it does not meet this condition.
• The state is unavailable/unreachable and one of the follow two sub-
conditions is met:
• The
pm.monitor.AlwaysReemitAlarm property is set to true. This
property is set to false by default.
• The duration of the
pm.monitor.AlarmReemitTimeout property
has elapsed since the last time OpenManage Network Manager emitted
a Monitor target state Event for this particular target and Monitor. By
default this property is 30, which means that by default even if a polling
target stays down for a period of several hours, it will only emit this
Event at most every 30 minutes. Even if you configure the Monitor to
poll this target more often than this and even if this target is unavailable
every polling cycle, it will still only emit this Event every 30 minutes,
unless you change this property.
29
One of these
conditions is met?
Available, unknown, or threshold reached? (State is unavailable/unreachable
and threshold for the number of unreachable/unavailable attempts was
reached).
This threshold comes from the # of Unreachable Attempts before update field
on the Editing Monitor. Note that this field covers both unreachable and
unavailable attempts.
30 Emit Monitor target
status Event
Emit the Monitor target status Event. If this routine is called to consider the
reachability of the target, it emits one of these event types:
• monitorTargetReachable
• monitorTargetUnreachable
If this routine is called to consider the availability of the target, it emits one of
these event types:
• monitorTargetUp (available)
• monitorTargetDown (not available)
See Understanding Event Life Cycle on page 353, the second process
(OMNM internal trap occurred) in the event life cycle diagram.
31
Return without
emitting Event
Return the origin of this routine without emitting an Event.
32
Return Return to the origin calling this routine.
33
Apply Retention
Policies
Begin the process that applies retention policies to drop tables and/or delete
rows from tables.
34
Drop old retention
tables
Drop the retention tables that are old according to the retention policy for the
monitor associated with each table.
Process Description