Integration Overview

Permissions

The following entitlements are required to make changes to integrations:

• InboundIntegrations_GlobalAccess — create, update, and delete inbound E-mail, API, and Chat Integration templates in your environment.
• OutboundIntegrations_GlobalAccess — create, update, and delete Outbound API Integrations and methods in your environment.

The user roles with access to these integration entitlements are Owner, App Admin, and Integrations Admin.

Overview

Relevant for Anyone connecting AlertOps to another system

AlertOps is highly flexible when it comes to both inbound and outbound integrations. Creating an integration and getting the most out of your monitoring stack takes just a matter of minutes.

AlertOps comes with several pre-built integrations across the most popular DevOps, SecOps, ITSM, Monitoring, and a wide range of other tools. Unlike most platforms, you are not limited to the pre-templated integrations — AlertOps also provides plug-and-play / custom Open REST APIs and Open Email APIs that let you integrate with virtually any tool or system in your stack, even if it's homegrown.

When an integrated system detects an issue, AlertOps executes predetermined notifications such as voice calls, messages, or emails to the appropriate personnel or customers. AlertOps also escalates through multiple devices and personnel until someone accepts the alert and resolves the issue.

Integration Types

Relevant for Anyone choosing how to connect a new system

AlertOps supports four integration types. The right one depends on what the source system can produce:

API Integrations

AlertOps is capable of ingesting data from any tool capable of interacting with a REST API. AlertOps provides REST APIs to integrate with virtually any software that can make HTTP requests.

Use this when the sender supports outbound webhooks. See Configuring API Integration and Custom API Integration.

Email Integrations

Email Integrations define the processing rules for creating AlertOps alerts from inbound emails. AlertOps can be integrated with any service capable of sending email alerts. Alerts are sent to the corresponding email address from monitoring tools — when AlertOps receives an email at this integration address, it executes an alert.

Use this when the sender only supports email. See Custom Email Integrations and Prebuilt Email Integrations.

Chat Integrations

Microsoft Teams provides collaboration tools for business teams; the Microsoft Teams integration with AlertOps connects to your group channels to resolve issues as a team.

Slack is another team communication tool which can be integrated with AlertOps to provide notification to group channels for collaborative resolutions.

Heartbeat Integrations

A Heartbeat Integration monitors signal activity coming from external sources. If there is no active signal — for example, a system going down — the heartbeat is interrupted and an alert is sent.

• Only one alert is sent for a Heartbeat alert.
• When heartbeat pulses resume for an open Heartbeat alert, the alert is closed automatically.
• You can create multiple Heartbeat Monitors; each one is tracked separately.

See AlertOps Heartbeat Monitoring for setup.

Inbound vs. Outbound

Relevant for Anyone choosing the direction of a new integration

Both directions are supported and most production tenants run both: