Release v0.7.0
This release uses OpenTelemetry Instrumentation for Java version 0.15.1. If you want to extend the instrumentation manually, use the OpenTelemetry Java API version 0.15.0. Consult the release notes linked above for upstream changes.
☢️ Breaking changes
- Property
otel.exporter
has been split intootel.trace.exporter
andotel.metrics.exporter
- There were lots of other configuration property name changes, please consult OpenTelemetry Javaagent release 0.15.0 for a more comprehensive list.
- Configuration property
otel.exporter.jaeger.service.name
no longer works with this release. To configure the service name please add theservice.name
key to the OpenTelemetry Resource, e.g. OTEL_RESOURCE_ATTRIBUTES=service.name=myservice.
📈 Improvements
- Collect WebLogic specific attributes #81
- Instrument Servlet API to add Server-Timing header #96
- Instrument Netty 3.8 to add Server-Timing header #100
- Enable Spring Batch item-level instrumentation by default #101
- Detect TomEE version #102
🛠️ Bug fixes
- Improve SQL sanitization performance and cache results open-telemetry/opentelemetry-java-instrumentation#2113 open-telemetry/opentelemetry-java-instrumentation#2094
- Use AWS trace propagator in AWS SDK v1 instrumentation without configuring it globally open-telemetry/opentelemetry-java-instrumentation#2117
- Propagate SQS trace context in AWS SDK v1 open-telemetry/opentelemetry-java-instrumentation#2114
- Enable SQS trace context propagation in Apache Camel open-telemetry/opentelemetry-java-instrumentation#2102