Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Performance Management Planning and Configuration Guide


4.3.4 Triggers for sending alarms

This subsection describes the triggers for sending alarms.

Organization of this subsection

(1) Monitoring the alarm status

An alarm event is sent when an alarm status changes. The alarm status of a record is determined based on the results of evaluating the instances in that record against the criteria specified as alarm conditions in the alarm definition. The highest severity level among the evaluation results is set as the alarm status of the record.

Figure 4-24 Monitoring the alarm status (example of monitoring disks) illustrates an example of sending alarms when an agent is monitoring the operating status of disks. In this example, the record that collects the performance data regarding the disks has two instances (for drive C and drive D).

If the agent detects an abnormality in drive C, the alarm status is set to Abnormal and the agent sends an alarm to the manager. If the agent detects an abnormality in drive D later, the agent does not send an alarm because the alarm status used for monitoring the disk is already Abnormal. If the status of drive D returns to Normal, the alarm status remains Abnormal and the agent does not send an alarm. When the statuses of both drives C and D return to Normal, the alarm status of the record changes to Normal and the agent sends a Normal alarm to the manager.

Figure 4‒24: Monitoring the alarm status (example of monitoring disks)

[Figure]

(2) Monitoring the operating status of each instance

An alarm event is issued if the alarm status of an instance of a record changes.

Suppose an agent is monitoring the operating status of disks. In such a case, the record that collects the performance data regarding the disks has two instances (for drive C and drive D). If the agent detects an abnormality in drive C while monitoring the operating status of instances, the agent sends an alarm status indicating Abnormal. If the agent detects an abnormality in drive D later, the agent sends another Abnormal alarm even though the alarm status has already been set to Abnormal because the status of the instance has changed. The agent also sends a Normal alarm when the status of the instance returns to Normal.

Figure 4‒25: Monitoring the operating status for each instance (example of monitoring disks)

[Figure]

The following versions of products are required to enable this function:

#

Required to bind an alarm table for sending alarms in units of instances.

(3) Constant monitoring of the alarm status

Every time an alarm evaluation is performed, an alarm event is sent if a record instance satisfies the abnormal criteria or warning criteria.

Figure 4‒26: Constant monitoring of the alarm status (example of monitoring disks)

[Figure]