Integrations
Using the Integrations capability you can connect data sources to provide data that helps gather insights for your environment.
The main Integrations page now has two tabs: the Manage integrations tab, and the Manage observer jobs tab.

On the Manage observer jobs tab, you can configure, schedule and manage jobs, and use integrations and observer jobs to collect topology data.

Incoming integrations provide data to IBM Cloud Pak for AIOps. Outgoing integrations report findings from IBM Cloud Pak for AIOps to supported ChatOps interfaces and ServiceNow. Some integrations are bidirectional. For example, to have a successfully operating instance of IBM Cloud Pak for AIOps, you might configure a Slack outgoing integration for ChatOps, a Falcon Logscsale incoming integration for log data, and a ServiceNow integration for change risk and similar ticket data.

Outgoing integrations must be publicly accessible. If your cluster is behind a firewall, for example, it must be tunneled through something, such as Secure Tunnel. For more information about Secure Tunnel, see Using Secure Tunnel for ChatOps. If you previously exposed your host for one outgoing integration, you do not need to configure it for other outgoing integrations.
For more information about prerequisites for specific outgoing integrations, see the following topics:
- Configuring Microsoft Teams for integration
- Configuring Slack applications for integration
- Configuring the ServiceNow App for IBM Cloud Pak for AIOps
- Mapping data
Note: When you configure integrations for IBM Cloud Pak for AIOps, your browser might give you an option to save key, token, or password-type fields. For security purposes, do not save these values. Turn off autofill or autosave settings in your browser, or exercise caution with these features.