Jaeger gRPC 🔗

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the jaeger-grpc monitor type to run a gRPC server that listens for Jaeger trace batches and forwards them to Splunk Observability Cloud (or the configured ingest host in the writer section of the agent config). By default, the server listens on localhost port 14250, but can be configured to anything.

Note

If you’re using OpenTelemetry, consider using the native OpenTelemetry Jaeger receiver. To learn more, see the Jaeger receiver documentation in GitHub .

Benefits 🔗

After you configure the integration, you can access these features:

View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Splunk Observability Cloud.
View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Use navigators in Splunk Infrastructure Monitoring.
Access the Metric Finder and search for metrics sent by the monitor. For information, see Search the Metric Finder and Metadata catalog.

Installation 🔗

Follow these steps to deploy this integration:

Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
Configure the integration, as described in the Configuration section.
Restart the Splunk Distribution of the OpenTelemetry Collector.

Configuration 🔗

To use this integration of a Smart Agent monitor with the Collector:

Include the Smart Agent receiver in your configuration file.
Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

See how to Use Smart Agent monitors with the Collector.
See how to set up the Smart Agent receiver.
For a list of common configuration options, refer to Common configuration settings for monitors.
Learn more about the Collector at Get started: Understand and use the Collector.

### Example

To activate this integration, add the following to your Collector configuration:

receivers:
  smartagent/jaeger-grpc:
    type: jaeger-grpc
    ... # Additional config

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

service:
  pipelines:
    metrics:
      receivers: [smartagent/jaeger-grpc]

Configuration settings 🔗

The following table shows the configuration options for this monitor:

Option	Required	Type	Description
`listenAddress`	no	`string`	The host:port on which to listen for traces. The default value is `0.0.0.0:14250`.
`tls`	no	`object (see below)`	TLS are optional tls credential settings to configure the GRPC server with

The nested tls config object has the following fields:

Option	Required	Type	Description
`certFile`	no	`string`	The cert file to use for tls
`keyFile`	no	`string`	The key file to use for tls

Metrics 🔗

The Splunk Distribution of OpenTelemetry Collector does not do any built-in filtering of metrics for this monitor.

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