ob-col/receiver/jaegerreceiver/README.md

Jaeger Receiver

Status
Stability	beta: traces
Distributions	core, contrib, aws, grafana, observiq, redhat, splunk, sumo
Issues
Code Owners	@jpkrohling

Receives trace data in Jaeger format.

Getting Started

By default, the Jaeger receiver will not serve any protocol. A protocol must be named under the protocols object for the jaeger receiver to start. The below protocols are supported, each supports an optional endpoint object configuration parameter.

• grpc (default endpoint = 0.0.0.0:14250)
• thrift_binary (default endpoint = 0.0.0.0:6832)
• thrift_compact (default endpoint = 0.0.0.0:6831)
• thrift_http (default endpoint = 0.0.0.0:14268)

Examples:

receivers:
  jaeger:
    protocols:
      grpc:
  jaeger/withendpoint:
    protocols:
      grpc:
        endpoint: 0.0.0.0:14260

Advanced Configuration

UDP protocols (currently thrift_binary and thrift_compact) allow setting additional server options:

• queue_size (default 1000) sets max not yet handled requests to server
• max_packet_size (default 65_000) sets max UDP packet size
• workers (default 10) sets number of workers consuming the server queue
• socket_buffer_size (default 0 - no buffer) sets buffer size of connection socket in bytes

Examples:

protocols:
  thrift_binary:
    endpoint: 0.0.0.0:6832
    queue_size: 5_000
    max_packet_size: 131_072
    workers: 50
    socket_buffer_size: 8_388_608

Several helper files are leveraged to provide additional capabilities automatically:

• gRPC settings including CORS
• TLS and mTLS settings

Remote Sampling

Since version v0.61.0, remote sampling is no longer supported by the jaeger receiver. Since version v0.59.0, the jaegerremotesapmpling extension is available that can be used instead.