6.3.18 Threshold definition file (ssothreshold.conf)
In the threshold definition file, define the initial value of a fixed threshold for threshold monitoring.
- Organization of this subsection
(1) Format
The following shows the format of the threshold definition file.
(2) Details of resource definition
Key name |
Value |
---|---|
rsc_id |
Specify a resource ID#1. |
threshold_monitoring <<N#2>> |
Specify whether to perform the threshold check on collected data for all subresources. Write Y to perform the check or N to not perform the check. |
When coding a resource definition, note the following:
-
Write as many resource definitions as the number of resources to be defined.
-
When omitting the threshold_monitoring definition, omit the whole definition, including the key name.
-
If the definition of a resource includes multiple definitions of threshold_monitoring, the definition written first is assumed to be valid, and the definitions written subsequently are assumed to be invalid.
-
If the definition file includes multiple resource definitions whose rsc_id value is the same, the definition written first is assumed to be valid, and the definitions written subsequently are assumed to be invalid.
(3) Details of subresource definition
Key name |
Value |
---|---|
threshold_submonitoring <<N#>> |
Specify whether to perform the threshold check on collected data for each subresource. Write Y to perform the check or N to not perform the check. Definition of this key overrides the definition of threshold_monitoring. |
threshold ((0, or integer or floating decimal point (double precision number) between ±1.00 x 10-2 to ±1.7976931348623157 x 10127)) |
Specify the warning threshold and critical threshold. Delimit each threshold with a semicolon (;). |
threshold_OVER <<1;1>> ((1 to 99)) |
Specify the number of times the warning threshold can be exceeded continuously and number of times the critical threshold can be exceeded continuously. Delimit each continuous over count with a semicolon (;). |
When coding a subresource definition, note the following:
-
After the resource definition, write as many subresource definitions as the number of subresources to be defined.
-
When omitting the threshold definition, omit only the value of the definition. The key name and equal sign, however, must be written. When omitting the threshold_submonitoring or threshold_OVER definition, omit the whole definition, including the key name.
-
If a subresource definition includes multiple definitions of threshold_submonitoring and threshold_OVER, the definitions written first are assumed to be valid, and the definitions written subsequently are assumed to be invalid.
-
If a resource definition includes more subresource definitions than the specified number of subresources, only the subresource definitions as many as the specified number of resources become valid, when counted from the top, and subsequent definitions become invalid.
-
If a resource definition includes less subresource definitions than the specified number of subresources, the subresource definitions that are not written are assumed to be omitted.
(4) Example
The following shows an example of a threshold definition file.