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

[dependabot]

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

Release notes

Sourced from opentelemetry-bom-alpha's releases.

Version 1.12.0

This release includes many breaking changes to the metrics SDK as we move towards marking its first stable release. Notably, if you configure metric Views or have written a custom metric exporter, many of the classes and methods will have been moved or renamed. There are still a few remaining cleanups targeted for the next release after which there should not be many. Thanks for bearing with us on this.

API

• New methods have been added to Context to propagate context for common Java 8 callback types
• AttributesBuilder.put now supports vararg versions for lists with AttributeKey
• Multiple metric async callbacks can be registered for the same instrument, and callbacks can be removed

SDK

• An issue with Android desugaring of the SDK has been worked around
• EXPERIMENTAL: Support for disabling resource keys with OTEL_EXPERIMENTAL_RESOURCE_DISABLED_KEYS
• Fixed handling of schemaUrl in Resource.toBuilder()
• BREAKING: Many changes to Data classes used during export
• BREAKING: Many view configuration methods have been removed

Metrics

• APIs deprecated in the previous release have been removed
• DEPRECATION: PrometheusCollector for exporting OpenTelemetry metrics with the prometheus client library has been deprecated
• EXPERIMENTAL: File-based configuration of views
• Prometheus exporter now supports JPMS modules

Logs

• DEPRECATION: LogData.getName has been deprecated for removal

Changelog

Sourced from opentelemetry-bom-alpha's changelog.

Changelog

Version 1.13.0 (2022-04-08)

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.

... (truncated)

Commits

• See full diff in compare view

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

Release notes

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

Version 1.12.1

This is a patch release on the previous 1.12.0 release, fixing the issues below.

🛠️ Bug fixes

• Elasticsearch rest client low cardinality span name (#5584)
• Fix possible deadlock (#5585)

Version 1.12.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.

🌟 New javaagent instrumentation

• Add Azure SDK instrumentation (#5467)

📈 Enhancements

• Use repository interface name in spring data operation name (#5352)
• Change the way Micrometer LongTaskTimer is bridged (#5338)
• Updates to http.server_name (#5369)
• Support forwarded proto field and x-forwarded-proto (#5357)
• Remove server span peer name (#5404)
• Add peer service support back to couchbase26 (#5451)
• Remove duplicative JAXRS HttpClient instrumentation (#5430)
• Add experimental thread attributes for logs (#5474)
• Add log4j 1.2 appender MDC capture (#5475)
• Capture logback formatted message (#5497)
• Add JBoss java.util.logging support (#5498)
• Disable the messaging receive span telemetry by default (#5500)
• Remove old experimental properties in CapturedHttpHeaders (#5524)
• Avoid conflicts in Micrometer description mapping (#5452)

🛠️ Bug fixes

• Fix another reverse lookup (#5393)
• Regression in loading the prometheus exporter (#5408)
• Fix muzzle failure on calls to primitive array clone (#5405)
• Fix regression in spring-scheduling span name (#5436)
• Fix android desugaring for HashMap.forEach (#5468)
• Fix duplicate class definition of ContextDataProvider (#5528)
• Do not propagate gRPC deadline when propagating OTel context via javaagent (#5543)

🧰 Tooling

• Split out CodeAttributesGetter (#5342)
• Add prometheus smoke test (#5417)
• Set custom gRPC client/server span name extractor (#5244)
• Split out DbClientAttributesGetter and SqlClientAttributesGetter (#5354)
• Add builders for setting optional attributes on HTTP extractors (#5347)
• Write http server tests in java (#5501)
• Deprecate CapturedHttpHeaders and replace it with builder methods (#5533)

... (truncated)

Changelog

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

Changelog

Version 1.13.0 (2022-04-19)

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)

... (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)

[gsmet]

Closing as this should be handled here: #24854 .

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.