Jaeger receiver 🔗

The Jaeger receiver gathers trace data in Jaeger format. The supported pipeline type is traces. See Process your data with pipelines for more information.

Get started 🔗

Note

This component is included in the default configuration of the Splunk Distribution of the OpenTelemetry Collector when deploying in host monitoring (agent) mode. See Collector deployment modes for more information.

For details about the default configuration, see Configure the Collector for Kubernetes with Helm, Collector for Linux default configuration, or Collector for Windows default configuration. You can customize your configuration any time as explained in this document.

Follow these steps to configure and activate the component:

Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

Install the Collector for Linux with the installer script

Install the Collector for Windows with the installer script

Install the Collector for Kubernetes

Configure the Jaeger receiver as described in the next section.
Restart the Collector.

Sample configurations 🔗

To activate the Jaeger receiver, add jaeger to the receivers section of your configuration file, as in the following sample configurations. By default, the Jaeger receiver doesn’t serve any protocol. You must name a protocol under the protocols object to start the receiver.

See Settings for more details.

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

Supported protocols 🔗

The Jaeger receiver supports the following protocols:

grpc. 0.0.0.0:14250 is the default endpoint.
thrift_binary. 0.0.0.0:6832 is the default endpoint.
thrift_compact. 0.0.0.0:6831 is the default endpoint.
thrift_http. 0.0.0.0:14268 is the default endpoint.

Optionally, you can configure an endpoint.

Advanced configuration 🔗

Use the UDP protocols, currently thrift_binary and thrift_compact, to set additional server options:

queue_size: Sets the maximum of not yet handled requests for the server. 1000 by default.
max_packet_size: Sets the maximum UDP packet size. 65_000 by default.
workers: Sets the number of workers consuming the server queue. 10 by default.
socket_buffer_size: Sets the buffer size of the connection socket, in bytes. 0 by default (no buffer).

For example:

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

Additional settings 🔗

The Jaeger receiver uses helper files for additional capabilities:

gRPC settings, including CORS. See more in GitHub at gRPC Configuration Settings
TLS and mTLS settings. Learn more in GitHub at TLS Configuration Settings .

Remote sampling 🔗

Since version 0.61.0, remote sampling is no longer supported. Instead, since version 0.59.0, use the jaegerremotesapmpling extension for remote sampling.

Settings 🔗

The following table shows the configuration options for the Jaeger receiver:

Troubleshooting 🔗

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers

Submit a case in the Splunk Support Portal .
Call Splunk Customer Support .

Available to prospective customers and free trial users

Ask a question and get answers through community support at Splunk Answers .
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

To learn about even more support options, see Splunk Customer Success .

Related Topics