Shipped · Observability

What jaegertracing/jaeger shipped

The public repository of Jaegertracing · github.com/jaegertracing/jaeger

Written by FoxPlug from the repository's own releases; not affiliated with Jaegertracing. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/jaegertracing/jaeger; Jaegertracing did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

Follow jaeger's weekly shipped digest

Week of October 5, 2026

What shipped

Why it matters

This week's release and the milestones behind it make storage behavior visible to API clients, so callers can see what a backend can search before issuing queries. Several fixes also close incorrect or unsafe behavior, including span search sorting, filter routing to SQL, and tracing data paths through remote storage and MCP tool calls. For people running Jaeger, the changes reduce surprising results and harden the storage and container layers.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Release v2.22.0 is out. Storage search capabilities now reach api_v3 over gRPC and HTTP, ClickHouse routes structured filters into SQL WHERE, and ES/OpenSearch no longer tie-break span search by document id by default. Filter tests and PromQL escaping also improved.

Post for LinkedIn

Release v2.22.0 is out this week. On top of it, Jaeger now exposes storage search capabilities over both api_v3 gRPC and HTTP, and the ClickHouse reader routes structured query filters into SQL WHERE clauses rather than folding them into a legacy shape. The Elasticsearch and OpenSearch reader declares span search, sorting and pagination capabilities, and the span search document id tie-breaker is now off by default. We also landed fixes for remote storage exports, MCP tool call spans, service name escaping in PromQL matchers, index name escaping in delete requests, and non-root primary groups for published images.

Week of September 28, 2026

What shipped

Why it matters

Span ordering is now fully implemented across query, storage gRPC, and backends, allowing callers to retrieve spans in their preferred order. Elasticsearch span search (RFC 0016 M4) progresses toward completion with tie-breaking, and release automation removes manual steps from the release process.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Span ordering ships in query, gRPC storage, and memory backend with RFC 0016 contract. Elasticsearch span search progresses (M4) with tie-breaking. Release automation drafts GitHub releases automatically.

Post for LinkedIn

This week adds caller-selected span ordering across the query service, gRPC storage layer, and backends, implementing RFC 0016's FindSpans contract with deterministic tie-breakers and order-bound continuation tokens. Elasticsearch span search implementation (RFC 0016 M4) now includes sort tie-breaking on backing index and document ID. Release automation improvements remove manual steps from the release process. Two breaking changes update Elasticsearch configuration structure and remote storage setup.

Week of September 21, 2026

What shipped

Why it matters

Span search moves from interface design into working storage backends, pagination establishes a shared format across readers, and dead-letter handling completes lossless pipeline support. Feature gates advance from experimental to stable as code matures, while infrastructure fixes address timeout handling and buffer serialization.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Span search reaches memory backend, pagination tokens standardized, and dead-letter handling completes lossless pipelines. Structured filters graduate to beta, native trace summaries to stable.

Post for LinkedIn

Week 40 advances RFC 0016 Span Search with FindSpans in memory storage and complete API v3 handlers, while RFC 0014 pagination establishes shared token format across readers. Dead-letter connector completes RFC 0007 lossless pipeline support. Feature gates progress: structured filters to beta, native trace summaries to stable. Fixes improve timeout handling and serialization correctness.

Week of September 14, 2026

What shipped

Why it matters

V2.21.0 is released with breaking changes and new span search capabilities. The paginated reader refactoring unifies how results flow through query and storage layers. Elasticsearch attribute indexing as numbers enables range queries to work correctly instead of lexicographically.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Jaeger v2.21.0 is out. Span search (RFC 0016) is underway, Elasticsearch attributes now index as numbers for range queries, and paginated results are generalized across all reader methods.

Post for LinkedIn

Jaeger v2.21.0 ships with breaking changes: v1 HTTP endpoints removed, AI config restructured, and unsupported ES configs rejected at startup. New capabilities include paginated reader results unified across all methods and span search (RFC 0016) implementation starting with RFC 0016 M2. Elasticsearch storage now indexes attribute values as numbers, fixing range queries that previously compared lexicographically.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-10-13.

Is this your repo? Ask us to remove this page.