Owner's Manual

774 Active Performance Monitor
Check Collect raw sysUpTime at the bottom of this screen to monitor that attribute.
Several monitors come seeded with the application. These include Core and Optional add-on
monitors. See
Core and Default Monitors on page 789 for a more about additional available
monitors and how to configure them.
Thresholds
This tab configures thresholds for the selected monitor. Here you can define value ranges reflecting
these thresholds for each monitored attribute, and give each range a name, color and severity. The
selected color appears in Dial charts for this monitor, but does not configure the color for any alarm
generated by crossing threshold for a range. See Core and Default Monitors on page 789 for an
explanation of the available attributes (they depend on the kind of monitor you are creating).
A threshold value is interpreted here as the lower boundary of some range. The upper boundaries
are calculated automatically to prevent gaps and simplify configuration. Lower boundaries are
inclusive while upper boundaries are exclusive.
You can also create more than one range with the same name. You can even create more than one
range with the same severity.
Each time the application collects data, it determines the correct threshold range for the attribute
value. When you base range checks on more than a single data point (with the
Range check based
on ___ value(s)
field), the application classifies the value as in a range previously determined until
criteria is met for a different range. If not enough data points exist (for example, the first time a
monitor runs), the application still determines a range, even one based on less data than the
Range
check based on ___ value(s)
selection.
For example, if you want an average of four data samples to determine whether some threshold has
been crossed, the first value collected by the monitor determines the range, based on what ranges
you specify in this
Thresholds screen. The next time the monitor runs, it determines the range
based on the average of two values, and so on until it reaches, and averages four values. Then it
continues to rely on the average of most recent four data samples to determine the current range.
This practice therefore establishes an initial threshold range when the monitor first runs.
The application produces an event when the range for a value changes. In other words: the event
occurs when the application determines a threshold has been crossed. This event also appears when
the monitor first starts, and its state changes from
no range to initial range .
The event is a
monitorAttributeTrend event from RedcellMonitor-MIB . The severity for the range
entered dictates the severity of the event. The default event definition produces an alarm with a
message showing monitor name, attribute name and range name.
A boolean value tracks each range in each attribute. These are
range results for the monitor. Only
one of the boolean range results values is true no matter how many ranges an attribute has. If you
configure multiple ranges to have the same name, then only one boolean range result exists for that
range name.