7.7.1 Managing response actions automatic execution status
The status management of response actions automatic execution depends on the type of response action being executed.
- Organization of this subsection
(1) When the command is executed in response action type cmd
The following figure shows the status transitions when response actions automatic execution is executed with response action type cmd.
|
When response action is executed automatically by specifying cmd as response action type, the normal status changes in the following order: "Wait in progress", "Obtaining the execution destination", "Execution control sending", "Saving DB", "Execution destination sending", "Queue", "Running", and "Ended".
If the command generation fails, the status is "Fail", if an error occurs, the status is "Send error" or "Error", and the process is terminated by JP1/IM-Manager (Intelligent Integrated Management Base).
The following tables show the status when response action type is cmd.
Item number |
Status |
Description |
---|---|---|
1 |
Wait in progress |
The execution request is managed in the transmit buffer. |
2 |
Retrieving a destination |
The system is acquiring response action execution control host to which the execution request is sent. |
3 |
Execution control sending |
Execution request is being sent to response action execution control (including during retry). |
4 |
Saving DB |
The execution request is saved in response action results-management database. |
5 |
Execution destination sending |
Execution is being sent to JP1/IM agent management base (including during retry). |
6 |
Queue |
The queued status of JP1/IM agent management base executable queue. |
7 |
Running |
The state in which the command is being executed. |
8 |
Ended |
The command has already been executed. Note that this status is independent of the exit code. |
10 |
Status unknown |
The action state is unknown because the state retrieval from response action results management database failed. Indicates that response action function could not get the action status. |
11 |
(blank) |
The action condition is set, but there is no action to be executed. |
12 |
Fail |
An error occurred prior to requesting execution to response action execution control, and the action cannot be executed. |
13 |
Send error |
Sending an execution request to response action execution control has failed, and the action cannot be executed. |
14 |
Error |
The request to execute JP1/IM agent management base was successful, but the action was terminated with an error. |
(2) When the command is executed in response action type restApi
The following figure shows the status transitions when response actions automatic execution is executed with response action type restApi.
|
When response action is executed automatically by specifying restApi as response action type, the normal status changes in the order of "Wait in progress", "Execution control sending", "Saving DB", "Executing" and "Ended".
If the command generation fails, the status is "Fail"; if an error occurs, the status is "Send error" or "Error", and the process is terminated.
The following tables show the status when response action type is restApi.
Item number |
Status |
Description |
---|---|---|
1 |
Wait in progress |
The execution request is managed in the transmit buffer. |
2 |
Execution control sending |
Execution request is being sent to response action execution control (including during retry). |
3 |
Saving DB |
The execution request is saved in response action results-management database. |
4 |
Running |
REST API is running. |
5 |
Ended |
REST API has already finished executing. |
6 |
Status unknown |
The action state is unknown because the state retrieval from response action results management database failed. Indicates that response action function could not get the action status. |
7 |
(blank) |
The action condition is set, but there is no action to be executed. |
8 |
Fail |
An error occurred prior to requesting execution to the linked Web servers, and the action could not be executed. |
9 |
Send error |
Sending an execution request to response action execution control has failed, and the action cannot be executed. |
10 |
Error |
The request to execute to the linked Web server was successful, but an error occurred during the action execution and the execution was terminated. |