Release v1.3.0

[mateuszrzeszutek]

---

⚠️ 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.

---

This discussion was created from the release Release v1.3.0.