Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 19, 2025

Bumps io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17 from 2.22.0-alpha to 2.23.0-alpha.

Release notes

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

Version 2.22.0

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

⚠️ Breaking Changes

  • AWS SDK 2.x attributes updated to align with semantic conventions (#15028) - The following attributes have been renamed: - aws.bucket.name (S3) → aws.s3.bucket - aws.queue.url (SQS) → aws.sqs.queue.url - aws.stream.name (Kinesis) → aws.kinesis.stream_name - aws.table.name (DynamoDB) → aws.dynamodb.table_names - aws.dynamodb.provisioned_throughput.read_capacity_unitsaws.dynamodb.provisioned_read_capacity (type changed from long to double) - aws.dynamodb.provisioned_throughput.write_capacity_unitsaws.dynamodb.provisioned_write_capacity (type changed from long to double) - aws.dynamodb.exclusive_start_table_nameaws.dynamodb.exclusive_start_table - aws.dynamodb.projection_expressionaws.dynamodb.projection - aws.dynamodb.scan_index_forwardaws.dynamodb.scan_forward - The following attribute types have changed: - aws.dynamodb.table_names: string → string[] - aws.dynamodb.consumed_capacity: string → string[] - aws.dynamodb.global_secondary_indexes: string → string[] - aws.dynamodb.local_secondary_indexes: string → string[] - aws.dynamodb.consistent_read: string → boolean - aws.dynamodb.table_count: string → long - aws.dynamodb.limit: string → long - aws.dynamodb.attributes_to_get: string → string[] - aws.dynamodb.segment: string → long - aws.dynamodb.total_segments: string → long - aws.dynamodb.count: string → long - aws.dynamodb.scanned_count: string → long - The following attributes are no longer emitted by default but can be enabled with otel.instrumentation.aws-sdk.experimental-span-attributes=true: - aws.queue.name (SQS) - aws.lambda.function.name (Lambda) - aws.lambda.function.arn (Lambda)
  • JDBC library data source instrumentation now disabled by default (#15074)
  • JMX state metrics unit changed from empty string to 1 to align with semantic conventions (#15093)
  • AWS SDK 1.x attributes updated to align with semantic conventions (#15094) - Only affects users with otel.instrumentation.aws-sdk.experimental-span-attributes=true - The following attributes have been renamed and are now emitted by default (no experimental flag required): - aws.bucket.name (S3) → aws.s3.bucket - aws.queue.url (SQS) → aws.sqs.queue.url - aws.stream.name (Kinesis) → aws.kinesis.stream_name - aws.table.name (DynamoDB) → aws.dynamodb.table_names
  • Finatra controller spans now disabled by default to match other controller spans (#15118)
  • Netty HTTP request wrapper class renamed from HttpRequestAndChannel to NettyRequest (#15247)
  • JSP compile spans now disabled by default to match other view spans (#15261)

🚫 Deprecations

  • TracingConsumerInterceptor and TracingProducerInterceptor deprecated in favor of new configurable interceptors (#14929)
  • Various builder methods updated to use UnaryOperator instead of Function<X, X> (#15101)
  • DbClientCommonAttributesGetter deprecated in favor of DbClientAttributesGetter (#15139)

🌟 New javaagent instrumentation

  • Add JFinal instrumentation (#15216)

📈 Enhancements

  • Avoid Unsafe usage on Java 23+ (#14855, #15091)
  • Update Azure SDK instrumentation so az.namespace can be used for sampling (#15068)
  • Spring Boot Starter: Add cache to reduce environment variable lookups (#15132)
  • HTTP instrumentations now emit semantic convention schema URL (#15144)
  • Added instrumentation support for AsyncHttpClient version 1.8 (#15195)
  • Instrumenter customizer now receives instrumentation type (#15227)
  • Added support for Spring Framework 7.0 (#15287, #15299, #15301, #15304, #15311, #15362, #15371)
  • Added span status customizer to incubating InstrumenterCustomizer API (#15288)
  • Added configuration options for sqlcommenter (#15169)
  • GraphQL instrumentation now records data fetcher errors (#15289)
  • Add http client url template customizer (#15217)
  • Introduce idiomatic JmxTelemetry API for JMX metrics library (#15220)
  • Add instrumentation for OpenTelemetry API incubator's ExtendedOpenTelemetry (#15178)

🛠️ Bug fixes

  • Fix missing peer.service in Netty HTTP spans (#14963)
  • Fix Couchbase span kind to be CLIENT instead of INTERNAL (#14995)
  • Link attributes are now bridged to the Java agent when using OpenTelemetry API (#15143)
  • Potential race condition in JFR runtime metrics initialization fixed (#15231)
  • Regression fixed related to context propagation when using Spring @EnableAsync (#15249)
  • Declarative configuration now uses snake_case for distro resource provider attribute name (#15260)
  • Logback appender fixed to capture Logstash StructuredArguments.entries() (#15341)

... (truncated)

Changelog

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

Changelog

Unreleased

Version 2.23.0 (2025-12-13)

⚠️ Breaking Changes

  • ActiveMQ Classic JMX metrics: rename attributes and metrics to align with semantic conventions (see PR description for specifics) (#14996)
  • Library instrumentation: remove previously deprecated methods from telemetry builders (#15324)
  • Logback: captureArguments no longer captures message template, use captureTemplate (#15423)
  • Play: disable controller spans by default, re-enable with otel.instrumentation.common.experimental.controller-telemetry.enabled=true (#15604)

🚫 Deprecations

  • Library instrumentation: deprecate setSpanNameExtractor() and setStatusExtractor() in favor of setSpanNameExtractorCustomizer() and setStatusExtractorCustomizer() (#15529)

🌟 New javaagent instrumentation

🌟 New library instrumentation

📈 Enhancements

  • Spring starter: add declarative config logging exporter (#14917)
  • Failsafe: add support for RetryPolicy (#15255, #15537)
  • GraphQL: add option to disable capturing query documents (#15384)
  • JMX metrics: allow any classpath resource path in rules (#15413)
  • Spring Boot actuator autoconfigure: support Spring Boot 4 (#15433)

... (truncated)

Commits

Dependabot compatibility score

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)

…j-appender-2.17

Bumps [io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17](https://github.com/open-telemetry/opentelemetry-java-instrumentation) from 2.22.0-alpha to 2.23.0-alpha.
- [Release notes](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md)
- [Commits](https://github.com/open-telemetry/opentelemetry-java-instrumentation/commits)

---
updated-dependencies:
- dependency-name: io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17
  dependency-version: 2.23.0-alpha
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Dec 19, 2025
@github-actions
Copy link
Contributor

🌟 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.

@apupier
Copy link
Contributor

apupier commented Dec 19, 2025

there is a long list of breaking changes, not sure if it can affect us, or existing Camel routes, or not in some ways

@squakez
Copy link
Contributor

squakez commented Dec 19, 2025

All tests executed correctly. I think we can merge safely.

@squakez
Copy link
Contributor

squakez commented Dec 22, 2025

@apupier which are the breaking changes you're referring to?

@apupier
Copy link
Contributor

apupier commented Jan 6, 2026

the ones listed in the release notes that we can see by expanding a section in the #20521 (comment) comment
image

@squakez
Copy link
Contributor

squakez commented Jan 7, 2026

Those seem to be attributes of the otel trace, so, not really a breaking change in camel. We probably can include a section in the upgrade doc to notify users about those potential changes when using otel components.

@squakez squakez merged commit 56be638 into main Jan 7, 2026
5 checks passed
@squakez squakez deleted the dependabot/maven/io.opentelemetry.instrumentation-opentelemetry-log4j-appender-2.17-2.23.0-alpha branch January 7, 2026 15:34
@squakez
Copy link
Contributor

squakez commented Jan 7, 2026

The changes mentioned there are really wider that the dependency which we are updating. They affect entirely the java agent and not the jar we're upgrading here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

camel-4 core-build-and-dependencies dependencies Pull requests that update a dependency file java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants