Release v0.11.0

[mateuszrzeszutek]

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.

🗒 General notes

• Micrometer dependency was updated to version 1.7.0.

☢️ Breaking changes

• The Splunk Distribution of OpenTelemetry Java Instrumentation now uses the OTLP span exporter as the default. The OTLP
  exporter supports the splunk.access.token configuration option and can be used to send spans directly to Splunk
  cloud. The default OTLP exporter endpoint is http://localhost:4317. You can still use the Jaeger exporter by
  setting OTEL_TRACES_EXPORTER=jaeger-thrift-splunk.
• We have also changed the default endpoint of the SignalFx metrics exporter: it now points to http://localhost:9943,
  which is the default endpoint of Splunk OpenTelemetry Connector
  deployed on localhost.
• The agent now uses W3C tracecontext as the default trace propagation
  mechanism; W3C Baggage is also enabled by default. You can switch to the previous B3
  propagator by setting OTEL_PROPAGATORS=b3multi.
• Deprecated configuration property splunk.context.server-timing.enabled has been removed. You can use
  splunk.trace-response-header.enabled instead.
• A lot of breaking changes were introduced to the javaagent tooling/instrumentation APIs - if you customize this project in any way please consult the upstream release notes for more details.

🌟 Enhancements

• The agent will now log a warning when the service.name resource attribute is not provided.
• Context is now correctly propagated to reactor-netty callbacks (e.g. HttpClient#doOnRequest()) - introduced in this upstream repo PR.

---

This discussion was created from the release Release v0.11.0.