Configuring ThousandEyes for OpenTelemetry

The ThousandEyes for OpenTelemetry allows a vendor-neutral, machine-to-machine connection between ThousandEyes and its clients. By exporting telemetry data in the OpenTelemetry (OTel) format—an industry standard—clients can utilize a broad range of frameworks for collecting and analyzing telemetry data from ThousandEyes.

Configuration Options

You can configure ThousandEyes for OpenTelemetry using the following options:

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.

  • When using the grpc endpointType, the URL target cannot contain paths. The following are examples of valid and invalid URLs:

    • Valid grpc - https://example.com

    • Invalid grpc - https://example.com/collector/v1/metrics

  • When using the http endpointType, 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://example.com/collector/v1/metrics

  • 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.

    • US region:

      • 52.52.142.26

      • 52.52.36.83

      • 13.56.245.241

      • 52.9.183.148

      • 3.220.243.232

      • 3.221.227.188

      • 3.218.27.195

      • 18.232.232.61

      • 35.168.54.3

      • 107.22.84.44

      • 44.197.76.117

      • 54.224.75.111

      • 54.205.59.175

    • EU region:

      • 3.127.8.252

      • 3.70.3.30

      • 18.158.163.183

      • 34.243.129.225

      • 108.128.60.238

      • 46.51.169.205

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.

PreviousThousandEyes for OpenTelemetryNextConfiguring ThousandEyes for OpenTelemetry Using the API

Last updated