Configuring ThousandEyes for Splunk Cloud or Enterprise

This section describes how to create a data stream to Splunk Cloud Platform or Splunk Enterprise or Splunk Observability Cloud. This enables you to start receiving ThousandEyes data in Splunk products.

Splunk offers three observability products:

Configuration Options

You can configure ThousandEyes for OpenTelemetry data streams to Splunk using the following options:

Migration of Existing Splunk Integrations

  • All existing Splunk Enterprise and Splunk Cloud Platform integrations created via API are migrated to Integrations 2.0.

URL Target Requirements

When you create a stream through API or UI, the URL target must satisfy the following conditions:

  • For a URL to be a valid target, it must be syntactically correct, reachable, and use the HTTPS protocol.

  • The URL target must be secured with an SSL/TLS certificate signed by a trusted Certificate Authority (CA). Self-signed certificates or certificates signed by an internal (non-public) CA are not considered valid for this purpose.

  • The URL target must match the exact final full URL (including the path if there is one) to which the metrics will be sent. For example:

    • Valid http - https://http-inputs-realm.splunkcloud.com:443/services/collector/event

  • The URL target must be reachable from the ThousandEyes platform at the IP addresses below. If the URL target is not reachable, the stream integration service rejects the creation request.

    • US1 region:

      • 13.56.245.241

      • 52.9.183.148

      • 18.232.232.61

      • 35.168.54.3

      • 107.22.84.44

      • 3.220.243.232

      • 3.218.27.195

      • 3.221.227.188

    • US2 region:

      • 3.141.159.49

      • 3.17.98.26

      • 3.134.227.22

      • 3.18.18.42

      • 3.13.54.169

      • 3.138.52.162

      • 52.27.149.70

      • 52.32.30.54

      • 52.89.210.182

      • 44.227.213.61

      • 35.155.240.202

      • 35.81.172.197

    • EU1 region:

      • 18.157.124.37

      • 3.70.3.30

      • 18.158.163.183

      • 35.158.19.241

      • 3.127.8.252

      • 46.51.169.205

      • 54.75.173.76

      • 54.217.22.60

      • 34.243.129.225

      • 54.216.15.243

      • 108.128.60.238

In the API, the URL target is referred to as the streamEndpointUrl. For more information on streamEndpointUrl, see the schema definition in the developer documentation.

Last updated