Jaeger

Description

This Jaeger destination configures an OTLP exporter to send traces to a Jaeger server for ingestion. Replaces the pre-existing Jaeger destination that utilized a Jaeger specific exporter.

Supported Types

MetricsLogsTracesBindplane Agent
v1.36.0+

Configuration

FieldDescription
HostnameHostname or IP address of the Jaeger server.
PortPort of the Jaeger server, either gRPC or HTTP depending on Protocol, to send OTLP data to. Read more.
ProtocolThe OTLP protocol to use when sending to the Jaeger server. Can be gRPC or HTTP.
CompressionCompression algorithm to use when sending data to the OTLP server. Ensure that the server supports the compression algorithm selected. Kinds of compression depend on Protocol.
Additional HeadersAdd additional headers to be attached to each request.
Enable TLSWhether or not to use TLS.
Skip TLS Certificate VerificationEnable to skip TLS certificate verification.
TLS Certificate Authority FileCertificate authority used to validate TLS certificates.
Mutual TLSWhether or not to use mutual TLS authentication.
Mutual TLS Client Certificate FileA TLS certificate used for client authentication.
Mutual TLS Client Private Key FileA TLS private key used for client authentication.

This destination supports the following retry and queuing settings:

Sending QueuePersistent QueueRetry on Failure

Example Configuration

Basic Configuration

For basic configuration, we specify the hostname of the Jaeger server traces are going to be sent to, as well as what protocol will be used (in this case gRPC).

Web Interface

observIQ docs - Jaeger OTLP Destination - image 1

Standalone Destination

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Destination
3metadata:
4  id: jaeger_otlp
5  name: jaeger_otlp
6spec:
7  type: jaeger_otlp
8  parameters:
9    - name: hostname
10      value: '0.0.0.0'
11    - name: protocol
12      value: 'grpc'
13    - name: grpc_port
14      value: '4317'
15    - name: enable_tls
16      value: 'false'

Advanced Configuration

This configuration is similar to the basic configuration but also utilizes TLS, Sending Queue, Persistent Queue, and Retry on Failure.

Web Interface

observIQ docs - Jaeger OTLP Destination - image 2 observIQ docs - Jaeger OTLP Destination - image 3

Standalone Destination

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Destination
3metadata:
4  id: jaeger_otlp
5  name: jaeger_otlp
6spec:
7  type: jaeger_otlp
8  parameters:
9    - name: hostname
10      value: '0.0.0.0'
11    - name: protocol
12      value: 'grpc'
13    - name: grpc_port
14      value: '4317'
15    - name: grpc_compression
16      value: 'gzip'
17    - name: enable_tls
18      value: 'true'
19    - name: ca_file
20      value: '/some_ca_file'
21    - name: retry_on_failure_enabled
22      value: 'true'
23    - name: sending_queue_enabled
24      value: 'true'
25    - name: persistent_queue_enabled
26      value: 'true'