open-telemetry/opentelemetry-java v0.15.0

Version 0.15.0 (RC)

on GitHub

0.15.0 is planned to be the final release before 1.0.0. It is a release candidate and should mostly reflect our final API.

General

☢️ Breaking Changes

• Methods and classes deprecated in 0.14.x have been removed.

🌟 Miscellaneous

• The opentelemetry-semconv module has been marked as -alpha and removed from the bom. This was done because the OpenTelemetry project has not decided on a specification for stability of semantic conventions or the specific telemetry produced by
  instrumentation.
• The items in the io.opentelemetry.semconv.trace.attributes.SemanticAttributes which were previously
  generated form the Resource semantic conventions have been deprecated. Please use the ones in the new
  io.opentelemetry.semconv.resource.attributes.ResourceAttributes class.

📈 Enhancements

• A new io.opentelemetry.semconv.resource.attributes.ResourceAttributes has been introduced to hold the
  generated semantic attributes to be used in creating Resources.

🌟 Miscellaneous

• The SemanticAttributes class has been moved to a new module: opentelemetry-semconv and repackaged into a new package:
  io.opentelemetry.semconv.trace.attributes. The old SemanticAttributes class will be removed in the next release.
• The SPI interfaces for OpenTelemetry have been deprecated. We are moving to a new auto-configuration approach with the
  new SDK auto-configuration module: io.opentelemetry.sdk.autoconfigure. This module should be considered the officially
  supported auto-configuration library moving forward.

SDK

🛠️ Bugfixes:

• The Jaeger exporters will now properly populate the process service name from the Resource service.name attribute.

☢️ Breaking Changes

• SamplingResult.Decision has been removed in favor of the io.opentelemetry.sdk.trace.samplers.SamplingDecision top-level class.
• Resource.merge(Resource) now will resolve conflicts by preferring the Resource passed in, rather than the original.
• The default Resource (accessible via Resource.getDefault()) now includes a fallback service.name attribute. The implication
  of this is that exporters that have configured fallback service names will only use them if the SDK is intentionally
  configured with a Resource that does not utilize the default Resource for its underlying Resource data.
• The Sampler is now specified when building the SdkTracerProvider directly, rather than being a part of the TraceConfig.

📈 Enhancements

• Resource.getDefault() now includes a fallback service.name attribute. Exporters that require a service.name
  should acquire the fallback from the default resource, rather than having it configured in.

🌟 Miscellaneous

• Going forward, OTLP exporter endpoint specifications must include a scheme, either http:// or https://.
  We will support endpoints without schemes until the next release, at which point not providing a scheme will generate
  an error when trying to use them. This applies to the use of system properties, environment variables, or programmatic
  specifications of the endpoints.
• The exportOnlySampled configuration of the BatchSpanProcessor has been deprecated and will be removed in the next
  release.
• The io.opentelemetry.sdk.resources.ResourceAttributes has been deprecated and will be removed in the next release.
  Please use the new io.opentelemetry.semconv.resource.attributes.ResourceAttributes class in the opentelemetry-semconv
  module.
• The serviceName configuration option for the Jaeger and Zipkin exporters has been deprecated. In the next release, those
  configuration options will be removed, and the fallback service.name will always be pulled from the default Resource.

Extensions

☢️ Breaking Changes

• The otel.bsp.schedule.delay.millis env var/system property configuration option for the batch span processor has been renamed to
  otel.bsp.schedule.delay to match the specification.
• The otel.bsp.export.timeout.millis env var/system property configuration option for the batch span processor has been renamed to
  otel.bsp.export.timeout to match the specification.

📈 Enhancements

• The opentelemetry-sdk-extension-autoconfigure module will now additionally register the auto-configured
  SDK as the instance of GlobalOpenTelemetry when used.
• The opentelemetry-sdk-extension-autoconfigure module now supports the otel.exporter.otlp.certificate configuration
  property for specifying a path to a trusted certificate for the OTLP exporters.