Bump io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha from 2.8.0-alpha to 2.9.0-alpha

[dependabot]

Bumps io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha from 2.8.0-alpha to 2.9.0-alpha.

Release notes

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

Version 2.8.0

This release targets the OpenTelemetry SDK 1.42.1.

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

• The unit on the opt-in Java 17 JFR-based metrics was updated from milliseconds to seconds to conform with the semantic conventions. If you are using the Java agent, this only affects you if you are opting in via otel.instrumentation.runtime-telemetry-java17.enable-all=true. (#12084, #12244)

📈 Enhancements

• Update Pulsar instrumentation to work with next Pulsar release (#11648)
• Capture network.peer.address in OkHttp 3.0 instrumentation (#12012)
• Add support for CXF 4.0 JAX-WS (#12077)
• Add rules for capturing Apache Camel metrics exposed by JMX MBeans (#11901)
• Make RocketMQ span status extractor delegate to the default extractor (#12183)
• Bridge log body any value (#12204)
• Add declarative config support for resource providers (#12144)

🛠️ Bug fixes

• Fix Javaagent doesn't work with java.net.spi.InetAddressResolverProvider (#11987)
• Fix Oracle UCP 11 metrics not emitted (#12052)
• Fix wrong database info captured while using Apache ShardingSphere (#12066)
• Fix RabbitMQ NullPointerException (#12109)
• Fix possible NullPointerException in Play instrumentation (#12121)
• Fix error span status for successful requests in Ktor (#12161)
• Make OpenTelemetryHandlerMappingFilter handle exceptions from ServletRequestPathUtils.parseAndCache() (#12221)
• Fix tracing CoroutineCrudRepository.findById (#12131)
• Fix capturing context in log4j library instrumentation with async logger (#12176)

🙇 Thank you

This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:

@​123liuziming @​allati @​crossoverJie @​dao-jun @​hermannpencole @​heyams @​huange7 @​jack-berg @​jackshirazi @​jaydeluca @​jeanbisutti @​jerrylincs @​JonasKunz @​laurit @​LikeTheSalad

... (truncated)

Changelog

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

Changelog

Unreleased

Version 2.9.0 (2024-10-17)

📈 Enhancements

• Allow JMX Insight reuse for remote connections (#12178)
• Add opentelemetry-semconv-incubating to bom-alpha (#12266)
• Bridge more incubating api (#12230)
• Jetty HttpClient 12: propagate context to all response listeners (#12326)
• Add Pekko Scheduler context propagation (#12359)
• Add Akka Scheduler context propagation (#12373)
• Add instrumentation for spring-cloud-aws SqsListener annotation (#12314)
• Align SpringConfigProperties with DefaultConfigProperties (#12398)
• Clear context propagation virtual field (#12397)
• The opt-in experimental attribute aws.requestId was renamed to aws.request_id (to match the semantic conventions) and it is now emitted by default. (#12352)
• Ability to set Logback argument capture with a property in Spring Boot Starter (#12442)
• Support experimental declarative configuration (#12265)
• Spring Boot Starter: Add auto configuration for spring scheduling instrumentation (#12438)
• Extract APIGatewayProxyRequestEvent headers for context propagation in AWS Lambda instrumentation (#12440)
• Support JMX state metrics (#12369)
• Allow method instrumentation module to trace methods in boot loader (#12454)

🛠️ Bug fixes

• Fix gc duration metric in runtime-telemetry-java17 (#12256)
• Fix vert.x route containing duplicate segments when RoutingContext.next is used (#12260)
• Fixes for latest mongo version (#12331)

... (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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)