TL;DR
- Breaking changes in metrics due to OpenTelemetry collector package upgrade.
- New features include UI base path auto-detection and configurable header forwarding for storage backends.
- Extensive experimental work on AI/MCP endpoints and ClickHouse integration for metrics and SPM.
Key Changes
Breaking Changes: Jaeger v2.18.0 includes significant breaking changes. Metrics have been altered due to an upgrade of all OpenTelemetry collector packages. Additionally, the min step API has been removed from the metricstore.
New Features: The update introduces auto-detection of the UI base path from the browser URL, enhancing user experience. For backend integrations, configurable header forwarding is now supported for both Elasticsearch/OpenSearch and gRPC storage backends, improving flexibility for secured environments.
Bug Fixes & Improvements: Several fixes address issues such as normalizing span_kind input, resolving ClickHouse v26 alias problems, and correcting missing spanhash values in Cassandra v2 conversions. Timeouts in Cassandra and SigV4 authentication failures for ES/OS writes have also been fixed.
Experimental Features: This release continues to push boundaries with experimental AI/MCP endpoints for dynamic contextual tooling. Notably, there’s extensive integration work for ClickHouse, including metric storage, Service Performance Monitoring (SPM) capabilities like getcallrates, geterrorrates, getlatencies, and TTL support.
Impact for QA Teams
QA teams must validate existing integrations against the new metrics structure due to OpenTelemetry collector upgrades. New header forwarding features require testing in various secure backend configurations. The experimental ClickHouse SPM features offer new avenues for performance and reliability testing, demanding early validation.
