Docs » Send alert notifications to third-party services using Splunk Observability Cloud

Send alert notifications to third-party services using Splunk Observability Cloud 🔗

In addition to sending alert notifications by email (see Manage notification subscribers), you can configure Splunk Observability Cloud to send alert notifications to the following third-party services:

Third-party

Link to documentation

Amazon EventBridge

See Send alert notifications to Amazon EventBridge using Splunk Observability Cloud

BigPanda

See Send alert notifications to BigPanda using Splunk Observability Cloud.

Jira

See Send alert notifications to Jira using Splunk Observability Cloud.

Microsoft Teams

See Send alert notifications to Microsoft Teams using Splunk Observability Cloud.

Opsgenie

See Send alert notifications to Opsgenie using Splunk Observability Cloud.

PagerDuty

See Send alert notifications to PagerDuty using Splunk Observability Cloud.

ServiceNow

See Send alert notifications to ServiceNow using Splunk Observability Cloud.

Slack

See Send alert notifications to Slack using Splunk Observability Cloud.

Splunk On-Call (VictorOps)

See Send alert notifications to Splunk On-Call using Splunk Observability Cloud.

Webhook

See Send alert notifications to a webhook using Splunk Observability Cloud.

xMatters

See Send alert notifications to xMatters using Splunk Observability Cloud.

You can also configure Observability Cloud to send alert notifications to a webhook. See Send alert notifications to a webhook using Splunk Observability Cloud.

These notification service integrations allow you to configure Observability Cloud to automatically send alert notifications to these third-party services and webhooks when a detector alert condition is met and when the condition clears.

Depending on the third-party service, the alert notification can create notifications, incidents, or issues, for example, based on information sent in the Observability Cloud alert notification.

For information about how to use detectors, events, alerts, and notifications, see Introduction to alerts and detectors in Splunk Observability Cloud.

Note

About naming your integrations

When a user adds an alert recipient to a detector, they choose from the notification service integration names you create when configuring these integrations. For this reason, provide descriptive and unique names for the integrations you create. This helps ensure that users get enough information from an integration name to be able to select the correct recipient for the alert notifications.