Release v0.9.0

This release uses OpenTelemetry Instrumentation for Java version 1.0.0. If you want to extend the instrumentation manually, use the OpenTelemetry Java API version 1.0.0. Consult the release notes linked above for upstream changes.

☢️ Breaking changes

• Logging injection now sets fields trace_id, span_id, and trace_flags, instead of traceId, spanId, and sampled open-telemetry/opentelemetry-java-instrumentation#2312

❗ Deprecation warning

• Property signalfx.auth.token has been renamed to splunk.access.token in #125. In this release both properties are accepted, but the next one will remove the deprecated signalfx.auth.token configuration.

🛠️ Bug fixes

• AWS Lambda instrumentation will now propagate from HTTP headers if X-Ray is disabled open-telemetry/opentelemetry-java-instrumentation#2222
• Apache Camel instrumentation will not throw an NPE in app code when SQS propagation is not enabled open-telemetry/opentelemetry-java-instrumentation#2250

📈 Improvements

• Added Windows TomEE image and test #122
• Updated README #123
• Added OpenJ9 smoke test Docker images #127

Release v0.8.0

This release uses OpenTelemetry Instrumentation for Java version 0.16.1. If you want to extend the instrumentation manually, use the OpenTelemetry Java API version 0.16.0. Consult the release notes linked above for upstream changes.

☢️ Breaking changes

• There were several configuration property name changes. Most notably, otel.trace.exporter has been renamed to otel.traces.exporter. For other configuration renames property please consult the SDK release notes.

📈 Improvements

• Instrument Netty 4.0 to add Server-Timing header #108

🛠️ Bug fixes

• Fixed NPE in Apache Camel instrumentation happening when propagating SQS context open-telemetry/opentelemetry-java-instrumentation#2250

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 into otel.trace.exporter and otel.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 the service.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

🧪 Test improvements

• Add Windows smoke tests for Jetty, Tomcat, GlassFish #87
• Add Windows smoke tests for WildFly #92
• Test all proprietary Docker images in CI #103

Release v0.6.0

This release uses OpenTelemetry Instrumentation for Java version 0.14.0. If you want to extend the instrumentation manually, use the OpenTelemetry Java API version 0.14.1. Consult the release notes linked above for upstream changes.

📈 Improvements

• Resource attributes are now exposed as system properties and available for use in logging patterns #76
• Agent jar no longer contains duplicate files #79
• WebLogic 12.1.3 is now present in the matrix and used in smoke tests #82
• AutoService is now used instead of plain service files #84
• Experimental Spring Batch instrumentation is now enabled by default #88

🛠️ Bug fixes

• Preconfigured custom propagators are no longer overridden by the agent open-telemetry/opentelemetry-java-instrumentation#2004

Release v0.5.0

This release uses OpenTelemetry Instrumentation for Java version 0.13.0. If you want to extend the instrumentation manually, use the OpenTelemetry Instrumentation for Java API version 0.13.1. Consult the release notes linked above for upstream changes.

This release contains no further changes apart from the upstream version.

Release v0.4.0

This release uses OpenTelemetry Instrumentation for Java version 0.12.0. If you want to extend the instrumentation manually, use the OpenTelemetry Instrumentation for Java API version 0.12.1. Consult the release notes linked above for upstream changes.

☢️ Breaking changes

• We use b3-multi propagation by default #41

🌟 New instrumentation

• Add server name and version to span attributes for Jetty (#46), Tomcat (#50), GlassFish (#51), WildFly (#57) and WebSphere Liberty (#53)

📈 Improvements

• Use alwaysOn() sampler by default #42
• Better documentation for migrating from deprecated SignalFx java tracing agent
• Use PropertySource SPI instead of home-grown default config #49
• Support for authentication token to send data directly to Splunk Ingest # 56

Release v0.3.3

Enable sending traces directly to ingest

Release v0.3.2

Use "always on" sampler for all traces

Release v0.3.1

Use b3multi as default propagator

Release v0.3.0

This release uses OpenTelemetry Java instrumentation v0.10.1. Please consult the release notes linked above for upstream changes.

☢️ Breaking changes

• Starting from this release we use Jaeger-Thrift as the default exporter! If you used one of the configuration option of the Zipkin exporter below, you have to change to to the corresponding Jaeger exporter option.

Zipkin	Jaeger
otel.exporter.zipkin.endpoint	otel.exporter.jaeger.endpoint
OTEL_EXPORTER_ZIPKIN_ENDPOINT	OTEL_EXPORTER_JAEGER_ENDPOINT
otel.exporter.zipkin.service.name	otel.exporter.jaeger.service.name
OTEL_EXPORTER_ZIPKIN_SERVICE_NAME	OTEL_EXPORTER_JAEGER_SERVICE_NAME

• We don't add splunk.instrumentation_library.XXX span attributes any more. Instead use standard OpenTelemetry otel.library.XXX attributes.