Configuring Netcool/Impact to link events to runbooks

Triggers map events to runbooks. Using triggers, an operations analyst can immediately execute the runbook that matches to an event. Netcool®/Impact is used to run the trigger service.

Attention: The instructions to configure Netcool/Impact only apply to a hybrid deployment of Netcool Operations Insight® where Netcool/Impact runs on premises. Netcool/Impact is automatically configured in a full deployment of Netcool Operations Insight on Red Hat® OpenShift®. For more information, see Installing on Red Hat OpenShift Container Platform.

A trigger specifies which events map to which runbook.

All information about a trigger, including the event filters, is stored in Netcool/Impact. Netcool/Impact monitors the incoming events from Netcool/OMNIbus. If an event matches the filter conditions of one or multiple triggers, then Netcool/Impact stores the runbook ID and the runbook parameter values in the event. Additional actions depend on the type of runbook:
Manual or semi-automated runbooks
The operational analyst can then use the right-click context menu to launch the matching runbook directly from the event.
Fully automated runbooks
Netcool/Impact runs the runbook via an API call to IBM Runbook Automation. The result is stored in the event field RunbookStatus and in the event journal. If needed, the operational analyst can use the right-click context menu to launch the runbook again.
The topics in this section provide instruction for the following tasks:
  • Install and configure the Netcool/Impact add-on for Runbook Automation.
  • Ensure that all required fields are added to the alerts.status table in Netcool/OMNIbus.
  • Add a custom menu entry for the Netcool/OMNIbus Event Viewer for launch-in-context.
  • Enable connectivity from Runbook Automation to Netcool/Impact for managing the triggers.
  • Enable connectivity from Netcool/Impact to Runbook Automation for running fully automated runbooks.
  • Add more Netcool/OMNIbus event sources to the realm of Netcool/Impact and Runbook Automation, and remove them again if needed.