Release v1.10.0

This is a regular release that tracks the upstream instrumentation repo v1.13.0. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.13.0. For manually adding custom metrics we suggest using Micrometer version 1.8.5. Please consult the release notes linked above for upstream changes.

🗒 General

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

🛠️ Bugfixes

• Fix NullPointerException on context tracking when JFR event on JDK 17 provides no thread - #743

🌟 Enhancements

• Added host.name and container.id tags to Micrometer metrics - #726
• Added support for exporting events in profiler in pprof format which can be enabled using the splunk.profiler.cpu.data.format setting - #684
• Added profiler setting splunk.profiler.max.stack.depth to limit maximum depth of exported stack traces - #739

Release v1.9.1

This release is a patch release based on OpenTelemetry Instrumentation for Java version 1.12.1.

🗒 General

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

🛠️ Bug fixes

• Elasticsearch rest client low cardinality span name (open-telemetry/opentelemetry-java-instrumentation#5584)
• Fix possible deadlock (open-telemetry/opentelemetry-java-instrumentation#5585)

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.