Send alert notifications to services using Splunk Observability Cloud

In addition to sending alert notifications via email, send alert notifications to other services, such as PagerDuty, Slack, and BigPanda.

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 service integrations.

The following table shows Splunk service integrations:

Notification service integrations allow you to configure Splunk Observability Cloud to automatically send alert notifications to third-party services and webhooks when a condition for a detector alert 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 Splunk 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: When a user adds an alert recipient to a detector, they can 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.

List of Splunk Observability Cloud IP addresses

The following table contains a list of the IP addresses that you can use to allow incoming traffic (such as alert webhook requests) from Splunk Observability Cloud realms. Use these IP addresses as sources on an allow list.
Note: As part of our ongoing infrastructure expansion, Splunk is adding new IP addresses (marked with * in the following table) to Splunk Observability Cloud realms. The new IP addresses will become active by November 1, 2025. If your organization uses IP allow lists to control network traffic, add these IP addresses to your existing allow lists by November 1, 2025 and keep the current IP addresses in your allow lists.

Realm

IP addresses

us0

  • 34.199.200.84/32

  • 52.20.177.252/32

  • 52.201.67.203/32

  • 54.89.1.85/32

  • 3.213.126.84/32*

  • 3.213.180.202/32*

  • 107.20.133.167/32*

  • 44.218.172.57/32*

us1

  • 44.230.152.35/32

  • 44.231.27.66/32

  • 44.225.234.52/32

  • 44.230.82.104/32

  • 52.25.165.141/32*

  • 100.22.10.37/32*

  • 44.244.87.29/32*

  • 52.35.147.71/32*

eu0

  • 108.128.26.145/32

  • 34.250.243.212/32

  • 54.171.237.247/32

  • 54.74.50.205/32*

  • 34.240.86.238/32*

  • 18.200.127.69/32*

eu1

  • 3.73.240.7

  • 18.196.129.64

  • 3.126.181.171

  • 3.65.69.124/32*

  • 52.28.246.163/32*

  • 3.64.236.188/32*

eu2

  • 13.41.86.83

  • 52.56.124.93

  • 35.177.204.133

  • 3.10.90.137/32*

  • 13.43.28.243/32*

  • 35.178.45.205/32*

jp0

  • 35.78.47.79/32

  • 35.77.252.198/32

  • 35.75.200.181/32

  • 54.199.72.126/32*

  • 54.65.248.210/32*

  • 35.78.155.194/32*

au0

  • 13.54.193.47/32

  • 13.55.9.109/32

  • 54.153.190.59/32

  • 52.63.153.198/32*

  • 13.238.129.162/32*

  • 52.63.252.167/32*

us2

  • 35.247.113.38/32

  • 35.247.32.72/32

  • 35.247.86.219/32

  • 35.212.245.144/32*

  • 35.212.164.197/32*

  • 35.212.148.158/32*

sg0
  • 3.0.226.159
  • 18.136.255.76
  • 52.220.199.72