Hitachi

JP1 Version 12 JP1/SNMP System Observer Description, Operator's Guide and Reference


2.2.3 Threshold monitoring

If you are monitoring resources based on the collection conditions that have been set, you can monitor whether the collected data exceeds given thresholds. If a given threshold is exceeded, an event can be issued or a command can be automatically executed.

Organization of this subsection

(1) Threshold monitoring methods

The following two threshold monitoring methods are available:

For the fixed threshold method, you must consider and set appropriate threshold values. For the statistical threshold method, you must consider and set the ratio of appropriate data. Generally, users can more intuitively understand fixed thresholds than statistical thresholds. Therefore, the fixed threshold method is preferable for the design of a monitoring system.

Regardless of the method, to change the threshold according to the time zone, you must link a task scheduler (Windows), cron (Linux), or a product that has a scheduler function (JP1/AJS3) with the SSO operation commands.

(2) Thresholds and resource statuses

Threshold monitoring of the resource monitoring function can monitor whether the resource collection value exceeds the threshold. You can set a warning threshold and a critical threshold. With these thresholds, you can check the resource status (Normal, Warning, or Critical). Note that there are some resources whose threshold is often exceeded momentarily. In such a case (in the event of a singularity), you can also set a continuous over counter so as not to change the resource status.

The following figure shows the relationship between the thresholds (warning and critical) and the resource statuses. This figure is an example for when the continuous over counters of the warning threshold and the critical threshold are both set to 3.

Figure 2‒19: Relationship between threshold and resource status

[Figure]

The following table describes how the resource statuses are judged.

Table 2‒12: How resource statuses are judged

Status

How the status is judged

Normal

The resource value is below#1 the warning threshold value. Alternatively, the number of times the resource value has consecutively gone above#2 the warning threshold does not exceed the value of the warning-threshold continuous over counter.

Warning

The number of times the resource value has consecutively gone above#2 the warning threshold exceeds the value of the warning-threshold continuous over counter, but the conditions for judging the status as Critical have not been met.

Critical

The number of times the resource value has consecutively gone above#2 the critical threshold exceeds the value of the critical-threshold continuous over counter.

Unknown

The collection status has become Postponing.

Non-monitoring

  • The collection status has become Completed, Impossibility, or Standing by.

  • The number of monitored instances being collected has decreased.

#1

Below a threshold includes the threshold.

#2

Above a threshold does not include the threshold.

A resource status change event can be issued when the resource status changes. For details on the events, see G. Events.

(3) Threshold verification

During initial deployment and the initial stage of operation, it is difficult to determine the optimal fixed thresholds and the ratio of data. Therefore, you might have to revise the thresholds (fixed thresholds or ratio of data). At this time, you can use the actual collection data to check how many times the resource status has changed to Warning or Critical based on certain values specified as thresholds and continuous over counters. You can specify the current values or any values for the thresholds and continuous over counters. After verification, the specified values can also be used for collection conditions.

(4) Automated action

Actions can also be automatically executed when the resource status changes. An automated action is a function that automatically starts commands that execute operations such as notification to the system administrator and data collection. You can also define variables in these commands. For details on the variables you can define, see H. Variables That Can Be Defined via Automated Action. Commands can be executed by superuser in Linux or by Administrator in Windows.

(5) Notes

(a) Automated actions in Windows

To execute a batch file on Windows, add cmd /q /c at the beginning of the command line. For example, to execute C:\temp\aaa.bat, specify cmd /q /c C:\temp\aaa.bat.

(b) Execution of an automated action at ssocolmng daemon process startup

An automated action is executed as indicated in the following table according to the resource status at ssocolmng daemon process startup.

Resource status at ssocolmng daemon process startup

Resource status for which an automated action is set

normal

normal

warning

warning

critical

critical

(c) Notes on statistical thresholds

In statistical threshold monitoring, the threshold becomes 0 in the following cases:

  • When initial value calculation is not performed

  • When collection data required for obtaining the statistical threshold does not exist during initial value calculation or regular calculation