5.3.5 Handling errors by viewing suggestions

To use the suggestion function to handle errors in your system:

1. Identify the location where a problem occurred in the Operating status area.

   You can see the location in red, orange, or yellow on the sunburst chart or the tree chart.

2. Click the IM management node for which the icon is displayed.

   A list of suggestions appears in the Suggestion tab.

3. Click the Suggestion button.

   The suggestion bars are activated, which you can use to handle the problem.

4. Click one of the suggestion bars to check the description of the suggestion and the previous execution history in the Suggestion details area.

   To check the details of the criteria, click the Show the case details button. The Case details window appears, where you can see the activation criteria of the suggestion.

5. Click the Execute button.

   The response action is taken. The name of the button turns into Running.

6. Check that the response action is complete.

   The name of the button turns into Execute. You can also check the completion of the response action through an email notification sent by an automated action of an event.

   • If you click the Suggestion button again after the response action is taken, the list of activated suggestions now appears in a deactivated state because the system status has been changed due to the execution of the action.

   • If a response action to change the status of the event to Processed when the system returns to normal is defined in the suggestion definition file, the applicable suggestion is activated.

   • If you execute the suggestion for which the response action to change the status of the event to Processed is defined, changing the status of the event to Processed will change the status of the node to Normal. Clicking the Suggestion button again shows the list of deactivated suggestions.

Important

• Response actions for the same IM management node and same suggestion ID cannot be executed simultaneously.

• If the jddupdatesuggestion command or the jddupdatetree command is executed while a response action is being executed, the response action will not terminate midway. Therefore, response actions that reference the IM management node or suggestion definitions may fail.

• If a JP1 user is deleted or JP1 user permissions are changed or deleted while a response action is being executed, command executions using JP1 user information, plug-in common methods, and the REST API may fail, causing the response action to fail.

• If the JP1/IM2 - Manager service is stopped while a response action is being executed, the JP1/IM2 - Manager service will not stop until the response action terminates, meaning it may take some time for the service to stop. If the REST API or commands that take time are executed with the response action, it is necessary to carry out processing asynchronously.

• If the JP1/IM2 - Manager service is stopped directly after the execution of a response action began, response actions of the following types may fail:

  - plugin (if using common methods related to JP1 events)

  - eventStatus

  Furthermore, if the REST API of JP1/IM is executed while the service is stopped, the status code of 500 is returned. As a result of this, the response action may fail.

To Page Top