Overview

Skill Level: Any Skill Level

This recipe explains a possible approach to use an on premise Omnibus as event source for the Cloud Event Management (CEM).

Ingredients

For this recipe, the on premise Omnibus should be available on the environment and a new Omnibus gateway installation should be allowed.

Optionally, in case there is an available Slack Team, CEM can be integrated to Slack to send incident info to a Slack channel.

Step-by-step

  1. Create the Cloud Event Management Service in Bluemix

    To create the new service, follow steps below:

    • Log in on IBM Bluemix;
    • Click on Catalog to list all available services;
    • Type “Cloud Event Management” on the search field and click “Filter”;
    • Click on the “Cloud Event Management” on the result page;
    • Change info as need and click “Create”;
    • Go back to your dashboard and the new service should be available;
    • Click on the “Cloud Event Management” service on your dashboard;
    • Click on “Get Started” to access options;
  2. Adding a New Event Source to CEM Service

    To add a new event source to the existing CEM service, follow steps below:

    • Inside CEM service, click on “Administration”;
    • Click on “Event Sources”;
    • Click on “Configure a new event source”;
    • Search for Netcool/OMNIbus and click “Configure”;
    • Enter a name for the event source integration;
    • Save the Webhook URL info on a safe place, you will need it later;
    • Download the Gateway install code using the link available in the CEM configuration page;
    • The downloaded file should be “omnibus-gateway-nco-g-cem-1.1.0.9.zip” or similar;
    • Click save;
  3. Installing and Configuring the Gateway

    Once downloaded the gateway install code, follow steps below to install and configure it:

    • Copy the install pack to the Omnibus server;
    • Unzip the gateway install pack;
    • Locate and open the README file. It describes how to install and configure and start the gateway;
    • The gateway can be installed using “IBM Installation Manager” as shown below:
      • /opt/IBM/InstallationManager/eclipse/tools/imcl \
        -c install com.ibm.tivoli.omnibus.integrations.nco-g-cem \
        -repositories /home/my_home_dir/omnibus-gateway-nco-g-cem.zip
    • Follow “Post-installation Configuration” steps also described in the README file. Main steps are shown below:
      • Create new fields in the alerts.status table.
      • Create filters in the table replication definition.
      • Copy $OMNIHOME/gates/cem/G_CEM.props to $OMNIHOME/etc.
      • Configure the following gateway properties by editing $OMNIHOME/etc/G_CEM.props.
    • Start the gateway as described in the README file. Example below:
      • $OMNIHOME/bin/nco_g_cem -messagelevel debug -messagelog stdout (for debug)
      • $OMNIHOME/bin/nco_g_cem & (for normal use)
  4. Overview of the Event Flow

    Once all steps described above are completed, the events should start flowing from the on premise Omnibus to the Cloud Event Management. By default, for each alert an incident should be created at CEM.

    The event flow presented below has IBM APM as event generator tool, but it is not restricted to one tool. The flow also describes an integration to a Slack channel, which is optional and it is described on the next step.

    Capture

  5. Optional: Enable CEM to Slack Integration

    There is an integration available to send incidents information to a Slack channel.

    To enable this integration, follow steps bellow:

    • Go to the Cloud Event Management service;
    • Navigate to Administration;
    • Go to Integrations;
    • Click on new channel connection;
    • Fill the Slack team to connect to, put the credentials, the channel and the integration will be available.

Join The Discussion