Release v0.10.0
This release uses OpenTelemetry Instrumentation for Java version 1.1.0. If you want to extend the instrumentation manually, we suggest using the OpenTelemetry Java API version 1.1.0. Please consult the release notes linked above for upstream changes.
☢️ Breaking changes
- Removed the deprecated
signalfx.auth.token
configuration property: it was replaced bysplunk.access.token
in the previous release.
#171
❗ Deprecated
- Configuration property
splunk.context.server-timing.enabled
was renamed tosplunk.trace-response-header.enabled
. The old property name still works, but it will be removed in the next release.
#185
🌟 Added
- The Splunk Distribution of OpenTelemetry Java Instrumentation now gathers basic application and JVM metrics. By default, this feature is enabled and is sending metrics to a localhost SmartAgent instance: you can change the endpointby setting an appropriate configuration option. You can find a more detailed explanation about the feature here.
#135, #136 - Add metrics for JDBC connection pool: Apache Commons DBCP2. Aside from JVM metrics mentioned above, the javaagent also collects Apache Commons DBCP2 connection pool metrics now.
#144, #146, #148
📈 Changed
- Recommend using
deployment.environment
resource attribute instead ofenvironment
.
#139 - The SignalFx Java Agent migration guide has been brought up-to-date.
#141, #183 - The repo README and documentation was significantly revamped. You'll now find much more information about the features and configuration of this project. We've also added a FAQ and troubleshooting sections that aim to answer the most common problems that may arise while using the Splunk Distribution of OpenTelemetry Java Instrumentation.
#152, #155, #169, #187, #188, #191, #201 - Updated OpenTelemetry and OpenTelemetry Java Instrumentation versions to 1.1.0.
#199