Configuring routing of events to destinations in IBM Cloud Event Notifications

Prereqs

• Read What is IBM Cloud Event Notifications?.

• Learn more about Working with alerts in IBM Cloud Logs.

• Create an IBM Cloud Event Notifications destination.

Define 1 or more topics

Topics are based on a publish and subscription model. The topic subscribes to event data based on conditions that you configure. The Event Notifications service handles the routing and delivering of alerts reliably to the correct destinations based on the subscriptions that you configure.

• Each topic is created under a registered source.
• Each topic can have its own set of rules, which routes the incoming payload to the respective topic.

When you configure a topic, you define the conditions that the topic monitors to see if the event meets its subscription criteria. For example, if you have multiple alert definitions in your IBM Cloud Logs instance that notify through the same slack channel, you can configure these alerts within the same topic.

Or, if you have multiple IBM Cloud Logs alert definitions that notify to different slack channels, you must configure one topic for each slack channel. Then, you need to include in each topic configuration the alerts to be notified to the associated slack channel.

Complete the following steps to create a topic:

1. In the console, click the Navigation Menu icon > Resource list > Developer Tools.

2. Select your instance of IBM Cloud Event Notifications.

3. In the IBM Cloud Event Notifications navigation, selet Topics.

4. Click Create.

5. Enter a name and a description for the topic.

6. Select a source.

   A source is a resource that is configured automatically in the Event Notifications instance when you configure an outbound integration in your IBM Cloud Logs instance.

7. Add rules to the topic to define which events that are generated by alerts are in scope of the topic.

   Choose any of the following options to configure rules that filter the event data that the topic subscribes to:

   • Option 1: Configure the event type, event subtype or event severity.

     You can choose an event type. To see the list of supported types, see [Event types]/docs/cloud-logs?topic=cloud-logs-cl-events-for-en#cl-events-for-en-types).

     You can choose an event subtype. To see the list of supported subtypes, see Event subtypes.

     You can choose a severity value. To see the list of supported severities, see Event severities.

   • Option 2: You can define advanced conditions which must follow JSONpath specifications. The correctly written rule will extract the appropriate data from the incoming request payload. Event Notifications supports the == operator for JSONPath evaluation.

   • Option 3: Configure the event type, event subtype or event severity, and advanced conditions.

   If you do not select any rules, a default rule is added, which means all notifications route to the topic by default. A rule must be configured so a topic does not subscribe to all event data. If you don't have this rule, subscribers can receive alerts and the associated data for every alert generated by the instance.

8. Click Create.

Define 1 or more destinations

A destination defines a notification channel that you can use to notify when an alert is triggered.

Destinations are custom protocols, which are either services or user reachable entities. For more information on supported destinations, see Supported destinations.

For information on how to create a destination, see Create an IBM Cloud Event Notifications destination.

Define 1 or more subscriptions

A subscription links 1 topic with 1 destination.

You must add subscriptions to define which events, that are configured in a topic, are routed to a destination.

For information on how to create a subscription, see Create an IBM Cloud Event Notifications subscription.