Outgoing integrations

Outgoing integrations enable IBM Cloud Pak for AIOps to communicate how your IT operations are performing against a baseline model that is established by you during model training. IBM Cloud Pak for AIOps uses this comparison to report anomalous activity to you in near real time.

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.

When you set up your outgoing ChatOps integration, you must configure two channels: a proactive channel that you want to use for notifications (from change risk, for example), and a reactive channel that you want to use for incidents and alerts.

Note: The ServiceNow integration type has optional incoming and outgoing facets.

For more information about configuring ServiceNow, Slack, and Microsoft Teams for your integrations, see the following topics:

• Microsoft Teams integration
  • Configuring Microsoft Teams applications for integration
• Slack integration
  • Configuring Slack applications for integration
• ServiceNow integration
  • Configuring the ServiceNow App for IBM Cloud Pak for AIOps
• SSH integration
• Email integration
• Ansible integration