Integrating with IBM SevOne Network Performance Management

You can use a generic webhook integration to integrate IBM Cloud Pak for AIOps with IBM SevOne Network Performance Management.

For details see Creating Generic Webhook integrations.

Configuring IBM SevOne Network Management System (NMS) to forward events to the webhook integration for SevOne

IBM SevOne NMS must be configured with a new webhook configuration to send alerts to the webhook integration for SevOne NMS.

Note: Instructions to configure the webhook with SevOne NMS can differ depending on your SevOne NMS version. For more information about using the SevOne Webhook Definition Manager and configuring alerts in SevOne NMS, see NMS 6.6 Guides and the SevOne NMS User Guide.

Note IBM SevOne requires the webhook destination to use a TLS certificate signed by a trusted Certificate Authority (CA).

  1. Log in to the IBM SevOne console.

  2. On the top menu, go to Events > Configuration > Webhook Definition Manager.

  3. On the Policy Browser page, click Configure Webhook Destination on the Policies panel.

  4. Complete the following steps from the Add Webhook Destination panel:

    1. Set a Webhook Destination Name, for example: IBM Cloud Pak for AIOps Webhook
    2. Set a Description, for example: Webhook integration for SevOne NMS
    3. You can obtain the webhook URL from the Integrations UI page.
    4. Select the Allow insecure webhook connection option if the webhook integration uses a self-signed certificate.
    5. Expand the Headers section and select Use Basic Auth. Then, set the Username and Password fields with the credentials set in Step 6) of Creating a Generic Webhook integration.
    6. In the Request Options, select POST as the Request Method, application/json as the Content Type, and use the following sample body:
        {
      "routes": ["IBM CloudPak for AIOps"],
      "host": "$deviceName",
      "description": "$alertMessage",
      "alertMessage": "$alertMessage",
      "check": "$policyName - $objectName",
      "cluster": "$clusterName",
      "alertId": "$alertId",
      "alertType": "$alertType",
      "alertState": "$alertState",
      "occurrences": "$occurrences",
      "assignedTo": "$assignedTo",
      "deviceId": "$deviceId",
      "deviceIp": "$deviceIp",
      "deviceName": "$deviceName",
      "deviceAltName": "$deviceAltName",
      "groupName": "$groupName",
      "objectId": "$objectId",
      "objectName": "$objectName",
      "objectAltName": "$objectAltName",
      "objectDescription": "$objectDescription",
      "pluginName": "$pluginName",
      "pluginDescription": "$pluginDescription",
      "policyId": "$policyId",
      "policyName": "$policyName",
      "thresholdId": "$thresholdId",
      "thresholdName": "$thresholdName",
      "linkURL" : "<DI_URL.com/redirect/v1/reports?reportName=Indicator%20Summary&$DIDataResources|View in Data Insight>",
      "triggeringConditions": $triggeringConditions,
      "closureMessage": "$closureMessage"
  }
    7. Click Test Definition to send a test HTTP event to the webhook integration. Test both the triggering condition and clear condition webhooks to ensure that the recieved response code is 200 or 204.
    • A 204 status code indicates that no payload is included in the HTTP response, but the integration is successful.
    • If a response code of 400 Bad request is received, check the JSON template that is configured. Ensure that the JSON does not contain any syntax errors.
    1. Click Save.

  5. Configure or create policies to send events to the webhook integration by selecting the webhook integration as the webhook destination. For each of the policies in the Webhooks section, select the webhook that was created in the previous step. Complete the selection for the Trigger Conditions and Clear Conditions tabs. By default, SevOne alerts configuration enables One Webhook per Alert option which only sends one webhook on the first trigger condition and not subsequent triggers. You can opt to select Override Webhook per alert and deselect One Webhook per Alert option to trigger webhook on each alert trigger to send alert updates to your webhook.