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 🔗
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:
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.
Supported protocols 🔗
The Jaeger receiver supports the following protocols:
0.0.0.0:14250is the default endpoint.
0.0.0.0:6832is the default endpoint.
0.0.0.0:6831is the default endpoint.
0.0.0.0:14268is the default endpoint.
Optionally, you can configure an
Advanced configuration 🔗
Use the UDP protocols, currently
thrift_compact, to set additional server options:
queue_size: Sets the maximum of not yet handled requests for the server.
max_packet_size: Sets the maximum UDP packet size.
workers: Sets the number of workers consuming the server queue.
socket_buffer_size: Sets the buffer size of the connection socket, in bytes.
0by default (no buffer).
Additional settings 🔗
The Jaeger receiver uses helper files for additional capabilities:
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.
The following table shows the configuration options for the Jaeger receiver:
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
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 .