github.com/open-telemetry/opentelemetry-collector-contrib/exporter/jaegerexporter

Deprecated Jaeger gRPC Exporter

Status
Stability	deprecated: traces
Distributions	core, contrib, grafana, redhat
Issues
Code Owners	@jpkrohling, @frzifus

This exporter is being deprecated and will be removed in July 2023 as Jaeger support OTLP directly.

Exports data via gRPC to Jaeger destinations. By default, this exporter requires TLS and offers queued retry capabilities.

Getting Started

The following settings are required:

• endpoint (no default): host:port to which the exporter is going to send Jaeger trace data, using the gRPC protocol. The valid syntax is described here

By default, TLS is enabled and must be configured under tls::

• insecure (default = false): whether to enable client transport security for the exporter's connection.

As a result, the following parameters are also required under tls::

• cert_file (no default): path to the TLS cert to use for TLS required connections. Should only be used if insecure is set to false.
• key_file (no default): path to the TLS key to use for TLS required connections. Should only be used if insecure is set to false.

Example:

exporters:
  jaeger:
    endpoint: jaeger-all-in-one:14250
    tls:
      cert_file: file.cert
      key_file: file.key
  jaeger/2:
    endpoint: jaeger-all-in-one:14250
    tls:
      insecure: true

Advanced Configuration

Several helper files are leveraged to provide additional capabilities automatically:

• gRPC settings
• TLS and mTLS settings
• Queuing, retry and timeout settings