Skip to content

Release v1.6.0
Compare
Choose a tag to compare
released this 01 Dec 18:02
· 1071 commits to main since this release
v1.6.0
b8fb63c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This release uses OpenTelemetry Instrumentation for Java version 1.9.1. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.9.1. For manually adding custom metrics we suggest using Micrometer version 1.8.0. Please consult the release notes linked above for upstream changes.

🗒 General notes

  • OpenTelemetry Java SDK and OpenTelemetry Instrumentation for Java dependencies have been updated to version 1.9.1.
  • Micrometer dependency has been updated to version 1.8.0.

🛠️ Bug fixes

  • Fixed Tomcat thread pool metrics in Tomcat 10.
  • Disabled correlation by span links in messaging instrumentations. Now the PRODUCER-CONSUMER spans will always have parent-child relationship.

🌟 Enhancements

  • The Micrometer bridge instrumentation now supports versions starting from 1.3.0.
  • A new Oracle Universal Connection Pool instrumentation has been added. The agent now collects and exports metrics for Oracle UCP connection pools.
  • Profiling: changed the default thread dump rate to 10 seconds (previously 1 second).
  • The Netty and Reactor Netty instrumentations have been significantly refactored. They can now capture lower-level client telemetry like DNS resolution and connection telemetry (by setting -Dotel.instrumentation.netty.always-create-connect-span=true or -Dotel.instrumentation.reactor-netty.always-create-connect-span=true) or SSL handshake telemetry (by setting -Dotel.instrumentation.netty.ssl-telemetry.enabled=true). The Reactor Netty HTTP client instrumentation will now report the lower-level spans as children of the main HTTP client span.
Assets 8
Loading
0 Join discussion