OpenTelemetry Collector Configuration

ThousandEyes for OpenTelemetry uses the OpenTelemetry Collector to export the ThousandEyes telemetry data.

This section describes the configuration used to export data. The configuration depends on the stream's type and endpointType.

• For streams with type set to opentelemetry and endpointType set to grpc, ThousandEyes uses an OTLP gRPC Exporter with the following configuration:

  exporters:
    otlp:
      endpoint: <stream.streamEndpointUrl>
      headers: <stream.customHeaders>
      tls:
         insecure: false
      retry_on_failure:
         enabled: true
         initial_interval: 1s
         max_interval: 30s
         max_elapsed_time: 180s

• For streams with type set to opentelemetry and endpointType set to http, ThousandEyes uses an OTLP HTTP Exporter with the following configuration:

  exporters:
    otlphttp:
      metrics_endpoint: <stream.streamEndpointUrl>
      headers: <stream.customHeaders>
      tls:
         insecure: false
      retry_on_failure:
         enabled: true
         initial_interval: 1s
         max_interval: 30s
         max_elapsed_time: 180s

• For streams with type set to splunk-hec, ThousandEyes uses a Splunk HTTP Event Collector (HEC) Exporter with the following configuration:

  exporters:
    splunk_hec:
      endpoint: <stream.streamEndpointUrl>
      token: <stream.customHeaders["token"]>
      splunk_app_name: "ThousandEyes OpenTelemetry"
      source: otel
      sourcetype: otel
      tls:
        insecure: false
      retry_on_failure:
        enabled: true
        initial_interval: 1s
        max_interval: 30s
        max_elapsed_time: 180s

Placeholders

• <stream.streamEndpointUrl> is replaced with the actual endpoint URL configured in the stream.

• <stream.customHeaders> is replaced with the actual custom headers configured in the stream.