Customizing event notifications

You can define custom notifications for events that occur in WebSphere Automation. Supported notification actions include sending emails and invoking webhooks, which can be used to automate processes that respond to events.

About this task

You must have access to the WebSphere Automation REST API.

Overview

To define a custom notification, you specify an action to occur (for example, sending an email, or invoking a webhook), and then you define a trigger that initiates the action when a certain event occurs (for example, when a new vulnerability is detected in a registered server).

The types of actions that are supported are:
A trigger detects an event and invokes an action. In WebSphere Automation, resource triggers detect when a particular resourceType is created, updated, or deleted. The resourceTypes in WebSphere Automation include:
  • action: an event within WebSphere Automation
  • asset: a registered server or Java SDK
  • bulletin: a security bulletin
  • fix: a fix pack or interim fix
  • installation: the process of installing a fix to resolve a vulnerability
  • investigation: the process of investigating a memory leak
  • vulnerability: a common vulnerability or exposure (CVE)
  • *: wild card, matches any of the previously listed resourceTypes

The event notification process

When a resource notification is published to one of the relevant topics, the notifier component does the following steps.
  1. Receives the notification.
  2. Queries the DB for any matching triggers.
  3. For each matching trigger:
    1. Evaluates the condition (if any)
    2. Resolves the variables in the action
    3. Writes the resolved action to disk (/tmp/messages/webhook)
  4. When a resource notification is published to one of the relevant topics:
    1. Triggers the Apache Camel File component to consume the files in /tmp/messages/webhook
    2. Sets the relevant properties on the exchange
    3. Uses the Camel HTTP component to invoke the target webhook