Release v1.9.0

This is a regular release that tracks the upstream instrumentation repo v1.12.0. Please see the upstream release notes for a comprehensive list of changes also included in this release.

🗒 General

• OpenTelemetry Instrumentation for Java has been updated to version 1.12.0.

🛠️ Bugfixes

• Fix servlet instrumentation to prevent overwriting Server-Timing header for internal spans - #694

🌟 Enhancements

• JvmHeapPressureMetrics are now part of exported JVM metrics - #686.
• Size reduction for call stack payloads for profiling TLAB events - #687

Release v1.8.2

This is a patch release on the previous 1.8.1 release. It fixes exporting histograms with fixed buckets.

Release v1.8.1

This release is a patch release based on OpenTelemetry Instrumentation for Java version 1.11.1.
It fixes a regression in loading the Prometheus exporter.

Release v1.8.0

This release uses OpenTelemetry Instrumentation for Java version 1.11.0. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.11.0. For manually adding custom metrics we suggest using Micrometer version 1.8.2. 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.11.0.

❗ Deprecations

• Deprecated splunk-otel-javaagent-all.jar use splunk-otel-javaagent.jar instead.

Release v1.7.3

This is a patch release on the previous 1.7.2 release. It fixes a bug that caused JFR events to appear out of order.

Release v1.7.2

This release is a patch release based on OpenTelemetry Instrumentation for Java version 1.10.1.
It contains several bug fixes, all listed in the page linked above.

Release v1.7.1

This release is exactly the same as v1.7.0. It was created to re-run our deployment process and publish the javaagent as docker image.

Release v1.7.0

This release uses OpenTelemetry Instrumentation for Java version 1.10.0. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.10.0. For manually adding custom metrics we suggest using Micrometer version 1.8.2. 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.10.0.
• Micrometer dependency has been updated to version 1.8.2.

❗ Deprecations

• Deprecated splunk.profiler.period.threaddump config setting in favor of GDI-spec compatible splunk.profiler.call.stack.interval.

🌟 Enhancements

• Added a new splunk.profiler.memory.enabled property that enables all memory profiling features.
• Implemented a sampler for allocation-related profiling events. It can be enabled by setting the splunk.profiler.memory.sampler.interval property. The default value is 1; set the value to 2 or higher to sample data every nth allocation event.

Release v1.6.1

This release is a patch release based on OpenTelemetry Instrumentation for Java version 1.9.2.
It introduces a fix for the reactor-netty connection leak caused by the faulty instrumentation (see open-telemetry/opentelemetry-java-instrumentation#4862).

Release v1.6.0

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.