Roadmap | Jaeger

The following is a summary of the major features we plan to implement. For more details, see the Roadmap on GitHub.
Currently, Jaeger uses a v1 Storage API, which operates on a data model specific to Jaeger. Each storage backend implements this API, requiring transformations between Jaeger’s proprietary model and the OpenTelemetry Protocol (OTLP) data model, which is now the industry standard.
As part of #5079, Jaeger has introduced the more efficient v2 Storage API, which natively supports the OpenTelemetry data model (OTLP), allows batching of writes and streaming of results. This effort is part of a broader alignment with the OpenTelemetry Collector framework, tracked under #4843.
For more information see the issue description.
GenAI can provide powerful capabilities for automatic analysis of tracing data.
There can be multiple product functions, with increasing order of complexity:
For more information see the issue description.
Jaeger will evolve beyond traditional distributed tracing to become the observability backbone for GenAI applications. This means natively handling large, multi-modal payloads with tiered storage and PII sanitization; serving as a registry for evaluation outcomes so quality metrics are traceable to specific agentic steps; enabling dataset curation and prompt/model version analytics directly from trace data; extending the query language to filter on quality scores and user feedback; and optimizing the UI for non-linear agentic workflows with DAG rendering and A/B trace comparison.
For more information see the issue description.
Data streams are the new hotness in Elasticsearch & OpenSearch to store append-only observability data. Data streams are well-suited for logs, events, metrics, and other continuously generated data.
For more information see the issue description.
Bring streaming analytics support directly into Jaeger backend, instead of requiring separate Spark/Flink data pipelines.
For more information see the issue description.
Allow clients to export partial spans, to support two use cases:
For more information see the issue description.
We need a dynamic configuration solution that comes in handy in various scenarios:
For more information see the issue description.