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

[dependabot]

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

Release notes

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

Version 2.9.0

This release targets the OpenTelemetry SDK 1.43.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.

📈 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)
• Fix context propagation for ratpack request body stream (#12330)
• Fix lambda instrumentation to forceFlush logs also (#12341)
• Can't add custom AttributeExtractor to Apache HttpClient 5 library instrumentation (#12394)
• Disable logback capture arguments by default (#12445)
• Add support for missing list properties in spring starter (#12434)

🙇 Thank you

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

@​aarrsseni @​AntonioLyubchev @​breedx-splk @​brunobat @​cleverchuk @​Dimagreg @​dubek @​egahlin @​encodedrose @​fabiolnh @​heyams

... (truncated)

Changelog

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

Changelog

Unreleased

Version 2.10.0 (2024-11-13)

🌟 New javaagent instrumentation

• Ktor 3 instrumentation (#12562)

🌟 New library instrumentation

• Ktor 3 instrumentation (#12562)

Migration notes

• Spring Boot Starter Scheduling instrumentation scope name changed from io.opentelemetry.spring-scheduling-3.1 to io.opentelemetry.spring-boot-autoconfigure to reflect the module's name.
• Default flush timeout for aws lambda javaagent instrumentation changed from 1 second to 10 seconds to match the flush timeout used in the aws lambda library instrumentation. (#12576)

📈 Enhancements

• Delegate loading of java package to platform loader (#12505)
• Set up virtual field transforms before otel sdk is initialized (#12444)
• Update azure-core-tracing-opentelemetry version and improve HTTP suppression to back off when Azure SDK tracing is disabled. (#12489)
• Ktor2 http client uses low level instrumentation (#12530)
• Add logback mdc instrumentation to spring boot starter (#12515)
• Run class load listener only once (#12565)
• Remove duplicate byte buddy classes to reduce agent jar file size (#12571)
• Support additional JVM arg syntax in service name resource detector (#12544)

🛠️ Bug fixes

• Fix derby directory connection string parser (#12479)
• Improve whitespace handling in oracle jdbc url parser

... (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 will merge this PR once it's up-to-date and CI passes on it, as requested by @wendigo.

---

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)

[wendigo]

@dependabot merge