What jaegertracing/jaeger shipped
Generated by FoxPlug from public activity — not affiliated with Jaegertracing.
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.