Bump opentelemetry-alpha.version from 1.13.0-alpha to 1.14.0-alpha

[dependabot]

Bumps opentelemetry-alpha.version from 1.13.0-alpha to 1.14.0-alpha.
Updates opentelemetry-bom-alpha from 1.13.0-alpha to 1.14.0-alpha

Release notes

Sourced from opentelemetry-bom-alpha's releases.

Version v1.13.0

This release targets the OpenTelemetry SDK 1.13.0.

Although we originally intended 1.13.0 to be the first stable release of the metrics SDK, we've postponed it out of caution due to a large number of changes in both the metrics SDK specification and the java implementation. This release should be considered a release candidate for the metrics SDK. There are several notable changes mentioned in the Metrics section. Additionally, please note that the Auto-configuration module now enables metric export by default via OTLP, i.e. by default otel.metrics.exporter is set to otlp instead of none.

API

• Fix TraceStateBuilder reuse bug.

SDK

• InstrumentationScopeInfo replaces InstrumentationLibraryInfo. Methods returning InstrumentationLibraryInfo are deprecated.
• Add ResourceBuilder#removeIf(Predicate) method for symmetry with AttributesBuilder.

Traces

• Span events that record exceptions are instances of ExceptionEventData.

Metrics

• BREAKING: Remove MetricReader factory pattern:
  • MetricReader instances, rather than MetricReaderFacotry, are registered with SdkMeterProviderBuilder. For example: SdkMeterProvider.builder().registerMetricReader(PeriodicMetricReader.builder(exporter).build()).
  • MetricReader does not support custom implementations. Built-in readers include: PeriodicMetricReader, PrometheusHttpServer, and for testing, InMemoryMetricReader.
• BREAKING: Several breaking changes metrics to the Data classes:
  • MetriaData returns InstrumentationScopeInfo instead of InstrumentationLibraryInfo.
  • MetricData factories classes have been moved internal.
  • Exemplar data classes have been migrated to interfaces, and deprecated methods have been removed.
  • PointData classes have been migrated to interfaces.
  • ValueAtPercentile has been converted to ValueAtQuantile to reflect specification.
  • Drop HistogramPointData utility methods for finding bucket bounds.
• BREAKING: Move InstrumentType and InstrumentValueType to io.opentelemetry.sdk.metrics package.
• BREAKING: Several breaking changes to the InstrumentSelector / View APIs:
  • InstrumentSelector / View and corresponding builders have been moved to io.opentelemetry.sdk.metrics package.
  • InstrumentSelector meter selection criteria has been inlined and MeterSelector has been removed.
  • InstrumentSelector criteria has been reduced to reflect specification. All fields are exact match, except instrument name which accepts wildcard * and ? matches.
  • If InstrumentSelectorBuilder#build() is called without any selection criteria, an exception will be thrown.
  • View baggage appending attribute processor has been removed. Available for experimental use via SdkMeterProviderUtil#appendFilteredBaggageAttributes.
  • Concept of AttributeProcessor has been moved internal.
  • If a View configures an aggregation that is not compatible with the instrument type of a selected instrument, a warning is logged and the View is ignored.
• BREAKING: Remove deprecated Aggregation#histogram(). Use Aggregation#explicitBucketHistogram() instead.
• Relax behavior around conflicting instruments. If you register two instruments with the same name but conflicting description, unit, type, or value type, both will be exported and a warning will be logged indicating the metric identity conflict. Previously, the second registered would have produced a noop instrument. Likewise, if two views are registered that produce instruments with conflicting names, or if an instrument conflicts with a registered view's name, both will be exported and a warning will be logged indicating the view conflict.
• BREAKING: Exemplars have been moved to internal. By default, exemplars are enabled with with_sampled_trace filter. This can be adjusted via experimental APIs via SdkMeterProviderUtil#setExemplarFilter.
• BREAKING: MetricExporter#getPreferredTemporality() has been removed and replaced with getAggregationTemporality(InstrumentType), which allows exporters to dictate the aggregation temporality on a per-instrument basis. MetricExporter#alwaysCumulative(InstrumentType) and MetricExporter#deltaPreferred(Instrument) are provided as utilities representing common configurations.
• Callbacks associated with asynchronous instruments with multiple matching views will only be called once per collection, instead of once per view per collection.
• PeriodicMetricReader will no longer call MetricExporter#export if no metrics are available.
• BREAKING: SdkMeterProviderBuilder#setMinimumCollectionInterval has been removed. Available for experimental use via SdkMeterProviderUtil#setMinimumCollectionInterval.
• Introduce lock ensuring that metric collections occur sequentially.
• Add min and max to HistogramDataPoint.

Logs

... (truncated)

Changelog

Sourced from opentelemetry-bom-alpha's changelog.

Changelog

Version 1.14.0 (2022-05-09)

The metrics SDK is stable! New stable artifacts include:

• io.opentelemetry:opentelemetry-sdk-metrics (also now included in io.opentelemetry:opentelemetry-sdk)
• io.opentelemetry:opentelemetry-exporter-otlp-metrics (also now included in io.opentelemetry:opentelemetry-exporter-otlp)
• io.opentelemetry:opentelemetry-exporter-otlp-http-metrics
• Metrics testing components have been moved from io.opentelemetry:opentelemetry-sdk-metrics-testing to the stable io.opentelemetry:opentelemetry-sdk-testing.

While the API of the metrics SDK is now stable, there are a couple of known issues that will be addressed in the next release:

• The start time is incorrect for delta metrics when the first recording for a set of attributes occurs after the first collections (#4400).
• Registering multiple readers results in incorrect metrics (#4436).

SDK

Traces

• Fix bug where non-runtime exception breaks BatchSpanProcessor.
• Fix bug preventing attribute limits from applying to exception events.

Logs

• BREAKING: Drop deprecated methods referencing InstrumentationLibraryInfo from Log SDK.

Metrics

• Instrument name is validated. If invalid, a warning is logged and a noop instrument is returned.
• Default unit is empty instead of 1. If an invalid unit is set, a warning is logged and empty is used.
• Ensure symmetry between type of PointData and their type of exemplars (double or long).
• BREAKING: Rename MetricReader#flush() to MetricReader#forceFlush().
• Introduce AggregationTemporalitySelector interface for selecting aggregation temporality based on instrument. MetricReader and MetricExporter extend AggregationTemporalitySelector.

SDK Extensions

• BREAKING: Remove deprecated option to specify temporality with otel.exporter.otlp.metrics.temporality. Use otel.exporter.otlp.metrics.temporality.preference instead.

... (truncated)

Commits

• See full diff in compare view

Updates opentelemetry-instrumentation-bom-alpha from 1.13.0-alpha to 1.14.0-alpha

Release notes

Sourced from opentelemetry-instrumentation-bom-alpha's releases.

Version 1.13.1

This is a patch release on the previous 1.13.0 release, fixing the issue(s) below.

🛠️ Bug fixes

• Fix duplicate class error on Android build (#5882)
• Fix spring-kafka single record instrumentation (#5904)

Version 1.13.0

This release targets the OpenTelemetry SDK 1.13.0.

Note that all artifacts other than io.opentelemetry.javaagent:opentelemetry-javaagent have the -alpha suffix attached to their version number, reflecting that they are still alpha quality and will continue to have breaking changes. Please see the VERSIONING.md for more details.

Migration notes

• Micrometer instrumentation is now automatically applied to spring-boot-actuator apps
• Some configuration properties have been renamed:
  • otel.instrumentation.common.experimental.suppress-controller-spans -> otel.instrumentation.common.experimental.controller-telemetry.enabled (important: note that the meaning is inverted)
  • otel.instrumentation.common.experimental.suppress-view-spans -> otel.instrumentation.common.experimental.view-telemetry.enabled (important: note that the meaning is inverted)
  • otel.instrumentation.netty.always-create-connect-span -> otel.instrumentation.netty.connection-telemetry.enabled
  • otel.instrumentation.reactor-netty.always-create-connect-span -> otel.instrumentation.reactor-netty.connection-telemetry.enabled
• Runtime memory metric names were updated to reflect semantic conventions
• Micrometer library instrumentation has been deprecated as it has been moved to the core repo and is now published under io.opentelemetry:opentelemetry-micrometer1-shim
• Library instrumentation entry points have been renamed from *Tracing to *Telemetry

🌟 New javaagent instrumentation

• GraphQL (#5583)
• JBoss Log Manager (#5737)
• Apache HttpClient 5.x async client (#5697)

🌟 New library instrumentation

• GraphQL (#5583)
• Ktor 2 (#5797)

📈 Enhancements

• Elasticsearch rest client low cardinality span names (#5584)
• Implement "Prometheus mode" for better micrometer->OTel->Prometheus support (#5537)
• Apply micrometer instrumentation to spring-boot-actuator apps (#5666)
• Sql sanitizer: handle double quoted table names (#5699)
• Spring Boot Starter service-name is constant (#5359)
• Update runtime memory metrics to reflect semantic conventions (#5718)
• change rpc type in apache dubbo (#5432)
• Rework context propagation to redisson async callback (#5748)
• Resolve end strategy after WithSpan method instead of before. (#5756)
• Allow scanning instrumented reactor publishers and only allow registe… (#5755)
• Faster type matching (#5724)
• Use UnsynchronizedAppenderBase as base class for our logback appender (#5818)

... (truncated)

Changelog

Sourced from opentelemetry-instrumentation-bom-alpha's changelog.

Changelog

Version 1.14.0 (2022-05-17)

Migration notes:

• The opentelemetry-log4j-appender-2.16 artifact has been renamed to opentelemetry-log4j-appender-2.17
• The opentelemetry-log4j-context-data-2.16-autoconfigure artifact has been renamed to opentelemetry-log4j-context-data-2.17-autoconfigure
• Micrometer library instrumentation has been removed as it has been moved to the core repo and is now published under io.opentelemetry:opentelemetry-micrometer1-shim
• The rxjava javaagent instrumentation names for suppression have changed to rxjava
• AgentListener#beforeAgent() has been deprecated, as it is not expect to be needed by extensions authors
• ConfigPropertySource has been deprecated in favor of ConfigCustomizer
• Several changes in the Instrumentation API
  • RequestMetrics has been renamed to OperationMetrics
  • RequestListener has been renamed to OperationListener
  • ErrorCauseExtractor#extractCause() has been renamed to extract()
  • ContextCustomizer and RequestListener start()/end() methods have been renamed to onStart()/onEnd()
• The opentelemetry-javaagent-instrumentation-api artifact has been merged into the opentelemetry-javaagent-extension-api artifact

🌟 New javaagent instrumentation

• Add jboss-logmanager mdc support (#5842)
• Spring-kafka single record instrumentation (#5904)
• Add metrics instrumentation for grpc (#5923)
• Add vertx-kafka-client instrumentation (#5973, #5982)
• Hide the GC runtime metrics behind an experimental config flag (#5990)
• Add HikariCP connection pool metrics (#6003)

🌟 New library instrumentation

• Add metrics instrumentation for grpc (#5923)
• Add HikariCP library instrumentation (#6023)

📈 Enhancements

... (truncated)

Commits

• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: area/dependencies.