IBM API Connect introduced the Business Engagement Platform feature in v10.0.9. The announcement of it can be found here which takes you through some of the use cases and capabilities Engagement makes available. A quick overview of it can also be found in this blog post. Since then additional features have been added, for example, APIC v10.0.10 added direct integration with Slack, PagerDuty and email. This has been expanded since v10.0.10 to now also include support using Amazon SNS for destinations. There have also been additional datasources added for long term summary data, config-sync and audit events.
Due to overwhelming demand the Engagement feature has been back-ported to LTS and is now available in APIC v10.0.8.3.
No additional pods or licensing is needed, it runs using the existing Analytics subsystem, though it does require internal storage to be enabled as that forms the engagement backend.
The Engagement feature allows you to create rules that can trigger actions to be sent to remote destinations when specific criteria are met. It supports a host of remote destination targets and now includes support for multiple different datasources.
Destinations
Engagement rules can trigger actions to the following destination types:
-
Custom webhooks
-
Email
-
Slack
-
PagerDuty
-
Amazon SNS
There are also examples in the documentation showing how to use custom webhooks to trigger Kafka, IBM Event Streams, IBM MQ, IBM Cloud Event Notification Service amongst others.
Datasources
Rules can be written based on the following data sources:
The addition of audit events as a datasource allows remote systems to be triggered when specific audit events happen within the API Connect platform, for example when a catalog is created, or a consumer subscription is created.
Upgrade to APIC v10.0.8.3 and see how you can use Engagement!
#APIConnect #integration #IBMAPIConnect #analytics