6.5.1 Automated action delay monitoring
The following problems might occur during execution processing of automated actions:
-
An action did not complete within the expected time.
-
An action has not completed after a considerable time.
These types of problems affect the execution processing not only of the action in question but of subsequent actions too.
By monitoring the execution time of an automated action (delay monitoring), you can reduce the time it takes for the operator to respond to a problem. Any delay will be reported to the operator by a JP1 event or notification command.
For details on setting up delay monitoring, see 6.5.3 Setting up execution monitoring.
- Organization of this subsection
(1) Delay monitoring start time and end time
Delay monitoring starts at the time when the JP1 event that triggers execution of the automated action arrives at JP1/Base on the manager.
Delay monitoring ends when the action reaches one of the following statuses:
-
Ended, Cancel, Kill, Fail, or Error
-
Ended (Miss) or Error (Miss)
If the action fails to reach one of the above statuses within the time set for delay monitoring, its status becomes Delay.
The following figure shows the time frame and statuses monitored during delay monitoring.
|
|
![[Figure]](GRAPHICS/CS036500.GIF)
When an automated action is re-executed at failover in a cluster system, the delay monitoring time and monitored statuses are no different from normal operation (the figure above). If you are using a cluster system, you must consider the time required for failing over the system when you set a delay monitoring time.
- Important
-
Delay monitoring does not apply to an automated action that is re-executed manually. This is because you are re-executing the action yourself, and can see when it starts and how long it takes.
Also, automated actions whose status is displayed as blank or as Deterrent are not monitored for execution delays.