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.

Release v1.5.0

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

🛠️ Bug fixes

• The Java agent no longer adds a security header to exported metrics when the SPLUNK_ACCESS_TOKEN is not configured.
  This means the agent should now work correctly with a collector that has token passthrough enabled.

🌟 Enhancements

• We have added instrumentation for WebLogic
  thread pools. The agent now collects and exports metrics for the WebLogic application server thread pools.
• We have also added instrumentation for Netty 4.1 that will add the server trace headers
  to the HTTP response.
• This release introduces the Java profiler. Keep in mind this feature is still experimental, and thus turned off by
  default; you can enable it by setting the splunk.profiler.enabled property to true. Find out more about Splunk
  profiler in its docs.

Release v1.4.0

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

🌟 Enhancements

• Added Restlet 1.0 instrumentation.

Release v1.3.1

This is a patch release on the previous 1.3.0 release. It bumps the OpenTelemetry Instrumentation for Java version to 1.5.2 and fixes the memory leak bug that manifested on 1.5.0 and 1.5.1 upstream versions when OpenTelemetry metrics exporter wasn't used.

Release v1.3.0

---

⚠️ There is a memory leak in the 1.3.0 Splunk Distribution of OpenTelemetry Java release. Please use the 1.3.1 release instead. ⚠️

---

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

🌟 Enhancements

• Middleware attributes (middleware.name and middleware.version) have been renamed to webengine attributes (webengine.name and webengine.version) to follow the OpenTelemetry specification.
• We have added instrumentations for c3p0 and Vibur DBCP connection pools. The agent now collects and exports metrics for both JDBC connection pools.
• We have also introduced instrumentations for Tomcat connector and WebSphere Liberty web request thread pools. The agent now collects and exports metrics for these application server thread pools.
• This release introduces the Micrometer bridge instrumentation. You can now use the Micrometer API inside your application to manually define custom metrics and the javaagent will export them. See the documentation for more details.
• The splunk.metrics.export.interval configuration property will now allow specifying time units; and if no units are specified then the value is treated as number of milliseconds. For example 30s means "30 seconds" and is equivalent to 30000.
• This release also introduces the muzzle safety checks to all Splunk instrumentations. Our instrumentations now offer exactly the same level of safety as the upstream OpenTelemetry instrumentations.

Release v1.2.0

This release uses OpenTelemetry Instrumentation for Java version 1.4.0. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.4.1. Please consult the release notes linked above for upstream changes.

🗒 General notes

• OpenTelemetry Java SDK has been updated to version 1.4.1.
• OpenTelemetry Instrumentation for Java has been updated to version 1.4.0.

🌟 Enhancements

• We have added instrumentation for HikariCP and Tomcat JDBC connection pools. The agent now collects and exports metrics for both JDBC connection pools.
• You can now set the service name using the OTEL_SERVICE_NAME environment variable and the otel.service.name system property. This removes the need of using OTEL_RESOURCE_ATTRIBUTES to set the service name.

Release v1.1.0

This release uses OpenTelemetry Instrumentation for Java version 1.3.0. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.3.0. Please consult the release notes linked above for upstream changes.

🗒 General notes

• OpenTelemetry Java SDK and OpenTelemetry Instrumentation for Java dependencies were updated to version 1.3.0.
• khttp instrumentation was moved from the upstream OpenTelemetry Instrumentation for
  Java repo to this one. We are now responsible for maintaining this instrumentation.

🛠️ Bug fixes

• The agent will always set exactly one Server-Timing header value; the bug where multiple copies of the same header
  value were set was fixed.
• Memory usage of the OpenTelemetry SDK has been significantly reduced; the agent will now use much less memory for tracing.

🌟 Enhancements

• Added internal_root_off sampler that will drop all traces that start with INTERNAL, CLIENT or PRODUCER span -
  the only top-level span kinds allowed are SERVER and CONSUMER. You can use this sampler by setting
  the otel.traces.sampler configuration property.
• Added a new spring-integration/spring-cloud-stream instrumentation: the agent will now correctly propagate context between Spring Cloud applications.

Release v1.0.0

This is the first stable release of the Splunk Distribution of OpenTelemetry Java.

Please note that although the Java agent itself is marked as stable, some of its components (e.g. metrics) are still experimental. Please consult the VERSIONING.md file for more details about our versioning strategy.

This release uses OpenTelemetry Instrumentation for Java version 1.2.0. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.2.0. Please consult the release notes linked above for upstream changes.

Release v0.12.0 (Release Candidate)

This release is intended to be the final release before 1.0.0.

This release uses OpenTelemetry Instrumentation for Java version 1.2.0. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.2.0. Please consult the release notes linked above for upstream changes.

☢️ Breaking Changes

• The metrics component will now be turned off by default. You can re-enable it by setting
  SPLUNK_METRICS_ENABLED to true.

🌟 Enhancements

• The agent will now set a resource attribute splunk.distro.version with its own version.
• The CloudFoundry buildpack file for Splunk Distribution of OpenTelemetry Java will now be built as a part of the
  release process and will be attached to the GitHub release.