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 toopentelemetry
andendpointType
set togrpc
, 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 toopentelemetry
andendpointType
set tohttp
, 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 tosplunk-hec
, ThousandEyes uses a Splunk HTTP Event Collector (HEC) Exporter with the following configuration:exporters: splunk_hec: endpoint: <stream.streamEndpointUrl> token: <stream.exporterConfig.splunkHec.token> splunk_app_name: "ThousandEyes OpenTelemetry" source: <stream.exporterConfig.splunkHec.source> sourcetype: <stream.exporterConfig.splunkHec.sourceType> index: <stream.exporterConfig.splunkHec.index> tls: insecure: false retry_on_failure: enabled: true initial_interval: 1s max_interval: 30s max_elapsed_time: 180s
PreviousOpenTelemetry Collector Data v2 Traces ExampleNextAutomatic Disabling of Failing Streaming Integrations
Last updated