This topic describes the System Threshold window for setting numeric
thresholds in IBM® Director.
Introduction
This
dialog enables you to define a numeric threshold for a selected managed system
or group.
Fields
- Name
- Identifies the threshold. This name identifies the threshold when you
view a listing of thresholds in the All Available Thresholds window.
- Description
- Enter additional descriptive information here, for example, list the criteria
or the purpose of the threshold. This information can be included as part
of the event text when an event is entered in the event log.
- Enabled to generate events
- Selecting this box activates the threshold when you save the information.
Leave this check box blank if you do not want to activate the threshold.
- Generate events on value change
- Selecting this check box will result in events being generated when the
value of the tracked attribute changes. A severity level of Warning is
assigned to the event.
All other threshold specification fields except for Minimum
Duration are disabled when you select this option because you
cannot specify a range of values and because the severity of the event is
fixed.
- Maximum queued events
- Specifies the number of events for this threshold to be held for the server
when the server is unavailable. This setting is ignored on agents that do
not support event queuing.
The Block queued events option in the Event Filter
Builder window allows you to specify whether blocked queued events are included
in an event filter.
- Minimum Duration
- Specifies the length of time these criteria must be met before an event
is triggered.
For example, if you select 5 minutes in this field and specify
a High Error threshold of 90.0, the value 90.0 must
be met or exceeded for 5 minutes without falling below 90.0 before an event
is triggered.
- Resend Delay
- Specifies the length of time that must transpire after an initial event
is triggered before a subsequent event is triggered.
For example, if you
select 1 hour in this field and these criteria cause an event to trigger,
another hour must elapse before a second event is triggered. The specified
criteria have to be met continuously during the interval for the event to
trigger when the interval expires. For example, if you specify a High-Error
range of 95.0 for CPU utilization and a resend delay of 1 hour, after the
initial event is triggered, CPU utilization must remain at 95.0 or greater
for 1 hour for the event to trigger again.
- Above or Equal
- High Error
- Generates a critical event if the resource value is equal to or greater
than the value specified in this field.
- High Warning
- Generates a warning event if the resource value is equal to or greater
than the value specified in this field.
- Below or Equal
- Low Warning
- Generates a warning event if the resource value is equal to or below the
value specified in this field.
- Low Error
- Generates a warning event if the resource value is equal to or below the
value specified in this field.
- Normal
- Generates a normal event only if an attribute changes from a selected
alert state (high-error, high-warning, low-error, or low-warning) back to
the normal state.