What jaegertracing/jaeger shipped
Written by FoxPlug from public releases; not affiliated with Jaegertracing. An automatic summary of the public release, pull request and commit data of github.com/jaegertracing/jaeger. Jaegertracing did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 21, 2026
What shipped
- The memory backend now supports FindSpans and search pagination, completing M3 of RFC 0016 Span Search as the first reader to declare SpanSearch capability. Pull request #9611
- The
api_v3FindSpans handler and HTTP route are now available, completing M2 of RFC 0016 Span Search. Pull request #9613 - RFC 0014 page tokens are now defined and returned by paginating readers, establishing the shared format for pagination across storage backends. Pull request #9655
- The
jaeger_storage_writerconnector now handles dead-letter rejection of spans in Elasticsearch, completing RFC 0007 M5. Pull request #9604 - Search query validation moved into the query service, eliminating duplicate validation logic across multiple API handlers. Pull request #9612
- A timeout from gRPC storage v2 configuration is now applied to storage calls, preventing indefinite blocking on remote storage hangs. Pull request #9638
- The native Elasticsearch trace summaries feature gate promoted from Beta to Stable. Pull request #9609
- The structured filters feature gate promoted from Alpha to Beta, enabling RFC 0005 filter syntax by default. Pull request #9607
- RFC 0018 proposes streaming responses for the API v3 HTTP gateway to avoid buffering full result sets. Pull request #9620
- Fixed TracesData.MarshalToSizedBuffer writing to buffer head instead of tail, correcting sized-buffer convention usage. Pull request #9629
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
- Memory backend now implements FindSpans with pagination support (RFC 0016 M3) Pull request #9611
- Added
api_v3FindSpans gRPC handler and HTTP route (RFC 0016 M2) Pull request #9613 - Defined RFC 0014 page tokens for paginating reader responses Pull request #9655
- Added
jaeger_storage_writerconnector for dead-letter span handling (RFC 0007 M5) Pull request #9604 - Centralized search query validation in query service Pull request #9612
- Apply configured timeout to gRPC storage calls Pull request #9638
- Promoted jaeger.es.nativeTraceSummaries to Stable Pull request #9609
- Promoted jaeger.query.structuredFilters to Beta Pull request #9607
- Changed SearchDepth and PageSize to unsigned in internal query types Pull request #9642
- Added shared pagination integration tests for direct and e2e modes Pull request #9664
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.
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
- Released v2.21.0 with breaking changes including removal of v1 HTTP endpoints, restructured AI MCP configuration, and rejection of unsupported Elasticsearch config keys at startup. Release
- Promoted the omitParentSpanIDReference gate to Beta for Elasticsearch/OpenSearch, controlling whether redundant synthetic CHILD_OF references are stored. Pull request #9586
- Added SearchSpans capability and FindSpans reader method as the first part of RFC 0016 span search implementation. Pull request #9578
- Generalized paginated reader results by replacing span-specific page results with generic PageChunk[T] across FindSpans, FindTraceIDs, and FindTraceSummaries. Pull request #9585
- Added Elasticsearch/OpenSearch support to index attribute values as numbers and order predicates on them instead of lexicographic comparison. Pull request #9321
- Fixed archive trace handling to prevent archiving traces that exist only in archive storage by reading ArchiveTrace requests only from primary storage. Pull request #9391
- Fixed double separator issue when index-prefix already ends with dash in Elasticsearch rollover and index cleaner tools. Pull request #9551
- Added validation to reject non-positive unit-count in jaeger-es-rollover lookback action to prevent cutoff date calculation errors. Pull request #9568
- Updated jaeger-idl to v0.12.0 to include FindSpans RPC entities for RFC 0016 M1. Pull request #9569
- Added labeled trace fixtures and end-to-end coverage tests for built-in query skills detect-n-plus-one and error-root-cause. Pull request #9263
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
- BREAKING: Removed v1 HTTP endpoints no longer used by the UI Release
- BREAKING: Replaced ai.enable_mcp with optional ai.mcp config block Release
- BREAKING: Reject five unsupported Elasticsearch configuration keys at startup Release
- Promoted omitParentSpanIDReference gate to Beta for Elasticsearch/OpenSearch Pull request #9586
- Added SearchSpans to capabilities and FindSpans to Reader interface (RFC 0016 M2 part 1) Pull request #9578
- Generalized paginated reader results with generic PageChunk[T] Pull request #9585
- Index attribute values as numbers in Elasticsearch/OpenSearch for correct range query ordering Pull request #9321
- Fixed archive trace handling to prevent archiving traces existing only in archive storage Pull request #9391
- Fixed double separator in index-prefix for Elasticsearch rollover and index cleaner Pull request #9551
- Validate non-positive unit-count in jaeger-es-rollover lookback action Pull request #9568
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.
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.