Skip to main content

Jaeger Receiver

Status Available in: core, contrib, k8s Maintainers: @yurishkuro Source: opentelemetry-collector-contrib

Supported Telemetry

Traces

Overview

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 = localhost:14250)
  • thrift_binary (default endpoint = localhost:6832)
  • thrift_compact (default endpoint = localhost:6831)
  • thrift_http (default endpoint = localhost:14268)
See our security best practices doc to understand how to set the endpoint in different environments. Examples:

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:
Several helper files are leveraged to provide additional capabilities automatically:

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.

Configuration

Example Configuration


Last generated: 2026-08-24