IBM integrations

Configuring the chart

The integration requires configuration of the chart parameters.

Configurable parameters
You use parameters to specify how the probe interacts with the device. You can override the chart's default parameter settings during installation.
Configuring the probe's HTTP client component
The IBM Tivoli Netcool/OMNIbus Message Bus Probe for Webhook Integrations can be configured to integrate with event sources which support REST API while also acting as a HTTP server to listen to HTTP notifications via the webhook URL. The probe can use REST API to pull data (or re-synchronize events) by sending HTTP requests.
Configuring the probe with a custom rules file
Enabling a secured connection with a TLS enabled event source
Enabling Ingress
Securing Ingress with TLS
Specifying a custom probe rules file
The Message Bus Probe for Kafka Integration helm chart and the Message Bus Probe for Webhook Integration helm chart allow you to specify a custom probe rules file by overriding the default rules file config map.
Configuring the JSON parser
The Message Bus Probe JSON parser can be configured to process different JSON event structures according to the endpoint set by the probe's transport module. This is useful when the event source system sends different JSON data structure depending on the API. For example, some event sources supports alarm query for clients to pull or re-synchronize alarms will return a batch or array of alarms while notification events are usually sent individually.

Parent topic: Message Bus Probe for Webhook Integrations Helm Chart