Jaeger OpenTelemetry Input Package
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless Observability
Preview
Preview
Serverless Security
Preview
Preview
Stack
Preview
9.4+
Preview since 9.4
| Version | 0.1.0 Availability Preview This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. (View all) |
| Subscription level What's this? |
Basic |
| Developed by What's this? |
Elastic |
| Minimum Kibana version(s) | 9.4.0 |
To use pre-release integrations, go to the Integrations page in Kibana, scroll down, and toggle on the Display beta integrations option.
The Jaeger OpenTelemetry Input Package for Elastic collects traces in Jaeger format using the OpenTelemetry jaegerreceiver. Package variables map to that receiver’s configuration (which protocols to enable, listen addresses, TLS for gRPC and Thrift HTTP, and UDP tuning). Choose settings in Fleet when you add this integration.
Source of truth for behavior: Protocol support (gRPC, Thrift HTTP, Thrift UDP variants), default endpoints, TLS and UDP options, and how multiple protocols interact are defined upstream—not duplicated here. Read the official jaegerreceiver README in OpenTelemetry Collector Contrib; for deeper detail use the receiver’s config.go in the same repository as described in the Elastic OTel input packages guide.
Jaeger versus OTLP: This input accepts Jaeger-formatted traces via the Jaeger receiver, not OTLP. For Jaeger product docs and migration notes, see Jaeger documentation.
Compatibility / migration: Many modern tracing SDKs and collectors prefer OTLP as the default export protocol, and some Jaeger-native components (especially legacy Thrift/agent-based paths) are being deprecated across the ecosystem. If your apps emit OTLP, use the otlp_input_otel package instead. If your apps emit Jaeger-native protocols (Jaeger gRPC or Thrift), this package is the right receiver. For background on the ecosystem shift, see OpenTelemetry’s “Migrating away from the Jaeger exporter in the Collector” post: https://opentelemetry.io/blog/2023/jaeger-exporter-collector-migration/
Requirements: Kibana 9.4.0 or later (traces support), Elastic Agent with Elastic Distribution of OpenTelemetry (EDOT).
Fleet applies generated collector configuration so the jaegerreceiver in EDOT listens according to your policy and forwards traces through the agent pipeline to Elasticsearch.
Changelog
| Version | Details | Minimum Kibana version |
|---|---|---|
| 0.1.0 | Enhancement (View pull request) Jaeger OTel input with per-protocol toggles, gRPC/Thrift HTTP/UDP (compact/binary), shared UDP tuning, and TLS for gRPC and Thrift HTTP |
9.4.0 |