3.5.3 Repeated event condition for the suppression of monitoring of a large number of events
The concept of repeated event condition, specifiable comparison attributes, and the concept of duplicate attribute value condition are the same as those described for the suppression of repeated event display. For details, see 3.4.3 Repeated event conditions. This subsection describes the settings items of repeated event condition the suppression of monitoring of a large number of events
- Organization of this subsection
(1) Setting items of repeated event condition (to suppress monitoring of a large number of events)
The following describes the settings items of a repeated event condition:
-
Event conditions
You can specify the JP1 event attributes to be compared when JP1/IM - Manager acquires monitoring-target events.
For details about the JP1 event attributes that can be specified, see 3.4.3(2) Event comparison attributes that can be specified in repeated event conditions.
-
Suppression items
You can specify what to suppress for the JP1 events that meet the repeated event condition. The operations that can be suppressed are as follows:
-
Consolidated display of repeated events in the Event Console window
-
Execution of the actions that are triggered by repeated events
To suppress the monitoring of a large number of events, you must specify both of the above items as suppression items. For details about the display in the event, see 3.4.6 Event list display during the suppression of repeated-event display. For details about the automated actions subject to the suppression of execution, see 3.5.8 Suppressing the execution of automated actions triggered by a large number of events.
-
-
Conditions for same attribute values
You can specify whether to suppress the display of events that meet a repeated event condition by grouping them by attribute. The condition to suppress events while grouping them by attribute is called a duplicate attribute value condition.
For details about the duplicate attribute value condition, see 3.4.3(3) Grouping repeated events by duplicate attribute value condition.
-
Threshold
You can set a threshold for determining whether the JP1 events meeting an event condition have occurred in large numbers. The threshold can be set by specifying the occurrence monitoring period and number of occurring events.
For the suppression of monitoring of a large number of events, set the threshold in the repeated event condition. The occurrence monitoring period can be specified in the range from 1 to 60 seconds. The number of occurring events can be specified in the range from 1 to 200 events.
For how the threshold is used, see 3.5.4 When the suppression of monitoring of a large number of events starts and 3.5.5 When the suppression of monitoring of a large number of events ends.
-
End monitoring period
You can set a period by which JP1/IM - Manager determines whether the occurrence of a large number of JP1 events has ended. The usage of the end monitoring period varies depending on whether the threshold is set.
The threshold is set for the suppression of monitoring of a large number of events. Therefore, JP1/IM - Manager determines that the occurrence of a large number of JP1 events has ended when the number of relevant JP1 events that occurred during the end monitoring period did not exceed the threshold. The end monitoring period can be specified in the range from 1 to 86,400 seconds. The default is 300 seconds.
For how the end monitoring period is used when the threshold is not set (in the case of the suppression of repeated-event display), see 3.4.5 When suppression of repeated-event display ends.
For how the end monitoring period is used when the threshold is set (in the case of the suppression of monitoring of a large number of events), see 3.5.5 When the suppression of monitoring of a large number of events ends.
-
Suppression start event and Suppression end event
You can specify whether to issue events that separately notify of the start and end of the suppression of monitoring of a large number of events. The event to notify of the start of monitoring suppression is called the suppression start event (event ID: 00003F58). The event to notify of the end of monitoring suppression is called the suppression end event (event ID: 00003F59). By default, neither notification event is issued. For details, see 3.5.10 Issuing events associated with the suppression of monitoring of a large number of events.
-
Checks for suppression to continue and Processing for when suppression continues
You can specify settings to check whether the suppression of monitoring of a large number of events continues at intervals of specified time (in seconds) or at every specified number of events. Also, you can specify settings to issue a JP1 event that notifies of continuation or terminates the suppression when the suppression is determined to be continuing. If, however, the suppression of monitoring of a large number of events is terminated, the number of occurring events per occurrence monitoring period is set to 1. As a result, a large number of events subject to monitoring suppression will be displayed in the event list, and unnecessary automated actions will be executed until the number of occurring events per occurrence monitoring period exceeds the threshold. Therefore, for the normal suppression of monitoring of a large number of events, the termination of monitoring suppression is not specified. If you want to terminate monitoring suppression when monitoring suppression is determined to be continuing, consider whether the termination of monitoring suppression causes problems before specifying settings for Processing for when suppression continues.
For the mechanism of issuing JP1 events as notifications when monitoring suppression is determined to be continuing, see 3.5.10 Issuing events associated with the suppression of monitoring of a large number of events.