Configuring Integrations

Integrations enable IBM Cloud Pak for AIOps to collect data from various sources, then communicate how your IT operations are performing against a baseline model that is established by your AI models. To have a fully functioning instance of IBM Cloud Pak for AIOps, you must configure both outgoing and incoming integrations. It is worth noting that ServiceNow is bidirectional.

Note: Each integration that you configure requires an additional 1 vCPU and 3GB memory. For example, if you configure five integrations then you will require an additional 5 vCPUs and 15GB memory.

For more information about integrations in general, click the following links:

• Integrations UI
• Integration types

For more information about integrations in general, including at a minimum how to create, edit, and delete a particular integration, click the corresponding link in the following list:

• Ansible integrations
• Appdynamics integrations
• AWS CloudWatch integrations
• Custom integrations
• Dynatrace integrations
• ELK integrations
• Falcon LogScale integrations
• Instana integrations
• Kafka integrations
• Mezmo integrations
• Microsoft Teams integration
• Netcool integrations
• New Relic integrations
• Observer jobs
• Optional integrations
• PagerDuty integrations
• Slack integration
• ServiceNow integration
• Splunk integrations
• SSH integrations
• Zabbix integrations

For ancillary information on integrations, see:

• Prerequisites for loading data from WebSphere log data sources
• Certificate management