Bump io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha from 1.27.0-alpha to 1.28.0-alpha

[dependabot]

Bumps io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha from 1.27.0-alpha to 1.28.0-alpha.

Release notes

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

Version 1.27.0

This release targets the OpenTelemetry SDK 1.27.0.

Note that many artifacts 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

• Jersey 3.0 instrumentation suppression keys have changed from jaxrs-2.0 to jaxrs-3.0, and from jersey-2.0 to jersey-3.0 (#8486)
• The opentelemetry-runtime-metrics artifact has been renamed and split into opentelemetry-runtime-telemetry-java8 and opentelemetry-runtime-telemetry-java17 (#8165, #8715)
• InetSocketAddressNetServerAttributesGetter and InetSocketAddressNetClientAttributesGetter have been deprecated (#8341, #8591)
• The new HTTP and network semantic conventions can be opted into using either the system property otel.semconv-stability.opt-in or the environment variable OTEL_SEMCONV_STABILITY_OPT_IN, which support two values:
  • http - emit the new, stable HTTP and networking attributes, and stop emitting the old experimental HTTP and networking attributes that the instrumentation emitted previously.
  • http/dup - emit both the old and the stable HTTP and networking attributes, allowing for a more seamless transition.
  • The default behavior (in the absence of one of these values) is to continue emitting the same HTTP and network semantic conventions that were emitted in 1.26.0.
  • Note: this option will be removed later this year after the new HTTP and network semantic conventions are marked stable, at which time the Java instrumentation version will be bumped from 1.x to 2.0, and the old HTTP and network semantic conventions will no longer be supported.

🌟 New javaagent instrumentation

• Quarkus RESTEasy Reactive (#8487)
• Reactor Kafka (#8439, #8529)

📈 Enhancements

• Use histogram advice in the Micrometer bridge (#8334)
• Disable by default gauge-based histograms in the Micrometer bridge (#8360)
• Specify ...jvm.gc.duration buckets using advice API (#8436)
• Make spanKindExtractor configurable in Ktor instrumentations (#8255)
• aws-sdk-2.2: Support non-X-Ray propagation for SQS (#8405)
• Implement HTTP resend spec for OkHttp 3 (#7652)
• Use jakarta.servlet.error.exception request attribute on jetty11 (#8503)
• Provide spring-boot-autoconfigure configuration metadata (#8516)
• Read AWS lambda tracing info from com.amazonaws.xray.traceHeader system property (#8368)
• Skip not decorator check for classes in boot loader (#8594)
• Change context propagation debug failures from error to warn (#8601)
• JavaScript Snippet Injection Support Servlet 5 (#8569)
• Faster type matching (#8525)
• Explicitly disable the logging exporter by default to override the upcoming SDK autoconfigure module change in 1.27.0 and preserve existing behavior (#8647)
• Support otel.sdk.disabled in the spring boot starter (#8602)
• Add OTLP log exporter to the OpenTelemetry Spring Starter (#8493)
• Suppress Spring Actuator instrumentation when micrometer instrumentation is suppressed (#8677)
• Replace "1" with the appropriate units and don't fall back to "1" if the unit is unknown (#8668)
• Added setOpenTelemetry method to log4j appender (#8231)

🛠️ Bug fixes

• Fix using logback mdc instrumentation along with SocketAppender (#8498)
• Fix failure when kafka metrics reporter is set to an empty string (#8523)
• Remove extra space from kubernetes client span name (#8540)
• Fix jetty context leak (#8552)
• Filter out scalar Mono/Flux instances (#8571)

... (truncated)

Changelog

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

Changelog

Unreleased

Version 1.28.0 (2023-07-12)

Migration notes

• Rename HTTP configuration settings (#8758)
  • otel.instrumentation.http.capture-headers.client.request → otel.instrumentation.http.client.capture-request-headers
  • otel.instrumentation.http.capture-headers.client.response → otel.instrumentation.http.client.capture-response-headers
  • otel.instrumentation.http.capture-headers.server.request → otel.instrumentation.http.server.capture-request-headers
  • otel.instrumentation.http.capture-headers.server.response → otel.instrumentation.http.server.capture-response-headers

📈 Enhancements

• Support latest armeria release (#8745)
• Support latest mongo release (#8785)
• Remove server.{address,port} from HTTP server metrics (#8771)
• aws-sdk-2.2.: Support injection into SQS.SendMessageBatch message attributes (#8798)
• Log4j and Logback appenders opt-in to using GlobalOpenTelemetry (#8791)
• aws-sdk-2.2: SNS.Publish support with experimental messaging propagator flag (#8830)
• support for adding baggage to log4j 2 ContextData (#8810)
• Micrometer bridge: interpret no SLO config as no buckets advice (#8856)
• Instrumentation for Elasticsearch 8+ (#8799)
• Add support for schemaUrls auto-computed from AttributesExtrators (#8864)
• Initialize appenders in the spring boot starter (#8888)
• Support reactor-netty 1.0.34+ (#8922)
• Rename messaging operation "send" to "publish" per spec (#8929)
• Extract query arguments without regex on lettuce 6 (#8932)

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[trask]

fixing...

[trask]

@cyrille-leclerc in case if you have a chance to review the changes I made to maven-extension

here's the upstream change that caused the breakage: open-telemetry/opentelemetry-java#5467

[trask]

thx @kenfinnigan!

[kenfinnigan]

No problem @trask