chore(deps-dev): Bump io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17 from 2.10.0-alpha to 2.11.0-alpha

[dependabot]

Bumps io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17 from 2.10.0-alpha to 2.11.0-alpha.

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17's releases.

Version 2.10.0

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

🌟 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 (#12512)
• Fix SpanKey bridging for unbridgeable span (#12511)
• Fix lettuce instrumentation and tests to pass against latest version (#12552)
• Fix Kafka initialization occasionally failed due to concurrent injection of OpenTelemetryMetricsReporter (#12583)

🙇 Thank you

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

@​AntonioLyubchev @​breedx-splk @​brunobat @​Cirilla-zmh @​e5l @​greatvovan @​heyams @​jaydeluca @​jeanbisutti

... (truncated)

Changelog

Sourced from io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17's changelog.

Changelog

Unreleased

Version 2.11.0 (2024-12-23)

Migration notes

In preparation for stabilizing HTTP library instrumentation soon:

• addAttributeExtractor methods in a few *TelemetryBuilder classes have been deprecated and renamed to addAttributesExtractor (which is how most of them were named already) (#12860)
• setEmitExperimental* methods in *TelemetryBuilder classes have been deprecated and moved to internal/experimental classes, see Javadoc @deprecated for exact relocation (#12847)
• ApacheHttpClient5* classes have been deprecated and renamed to ApacheHttpClient* (#12854)
• RatpackTelemetry* classes have been deprecated and split into RatpackClientTelemetry* and RatpackServerTelemetry* (#12853)
• SpringWebfluxTelemetry* classes have been deprecated and split into SpringWebfluxClientTelemetry* and SpringWebfluxServerTelemetry* (#12852)
• ArmeriaTelemetry* classes have been deprecated and split into ArmeriaClientTelemetry* and ArmeriaServerTelemetry* (#12851)
• *KtorClientTracing* and *KtorServerTracing* have been deprecated and renamed to *KtorClientTelemetry* and *KtorServerTelemetry* (#12855)
• Experimental opt-in attribute spring-webflux.handler.type was removed in favor of standard code.* attributes (#12887)

📈 Enhancements

• Map lettuce 5.1 db.namespace to db.name (unless using experimental database semconv stability opt-in) (#12609)
• Log4j2: add option to fill code attributes (#12592)
• Fill jvm.thread.state attribute for jvm.thread.count metric on jdk8 (#12724)
• Update Spring Scheduling code.* attribute extraction for latest release of Spring Scheduling (#12739)
• Add jctools classes to reflect-config.json for better native image support (#12736)
• Support Pulsar Client send message with transaction (#12731)
• Implement reading of simple key-value Logstash JSON Marker attributes (#12513)

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

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run

• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.

• Build and test logs are available in the Summary page. Only Apache Camel committers have access to the summary.

• ⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.