Skip to content

Conversation

@dependabot
Copy link
Contributor

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

Bumps io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha from 2.21.0-alpha to 2.23.0-alpha.

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha'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-instrumentation-bom-alpha'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

You can trigger a rebase of this PR 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)

…om-alpha

Bumps [io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha](https://github.com/open-telemetry/opentelemetry-java-instrumentation) from 2.21.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-instrumentation-bom-alpha
  dependency-version: 2.23.0-alpha
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the area/dependencies Pull requests that update a dependency file label Dec 15, 2025
@quarkus-bot
Copy link

quarkus-bot bot commented Dec 15, 2025

/cc @brunobat (opentelemetry), @radcortez (opentelemetry)

@quarkus-bot
Copy link

quarkus-bot bot commented Dec 15, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit e804b3a.

Failing Jobs

Status Name Step Failures Logs Raw logs Build scan
✔️ JVM Tests - JDK 17 Logs Raw logs 🔍
✔️ JVM Tests - JDK 21 Logs Raw logs 🔍
JVM Tests - JDK 21 Semeru Build Failures Logs Raw logs 🔍
✔️ JVM Tests - JDK 25 Logs Raw logs 🔍

You can consult the Develocity build scans.

Failures

⚙️ JVM Tests - JDK 21 Semeru #

- Failing: extensions/panache/hibernate-orm-panache-kotlin/runtime 
! Skipped: devtools/bom-descriptor-json extensions/panache/hibernate-orm-panache-kotlin/deployment 

📦 extensions/panache/hibernate-orm-panache-kotlin/runtime

Failed to execute goal org.jetbrains.kotlin:kotlin-maven-plugin:2.2.21:compile (compile) on project quarkus-hibernate-orm-panache-kotlin: Compilation failure


Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 extensions/smallrye-reactive-messaging/deployment

io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector - History

  • Expecting actual: ["-4","-5","-6","-7","-8","-9","-10","-11"] to start with: ["-3", "-4", "-5", "-6"] - java.lang.AssertionError
Details
java.lang.AssertionError: 

Expecting actual:
  ["-4","-5","-6","-7","-8","-9","-10","-11"]
to start with:
  ["-3", "-4", "-5", "-6"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:36)

⚙️ JVM Tests - JDK 17 Windows

📦 extensions/micrometer-opentelemetry/deployment

io.quarkus.micrometer.opentelemetry.deployment.compatibility.MicrometerTimedInterceptorTest.testTimeMethod_UniFailed - History

  • Stream has no elements - java.lang.IllegalArgumentException
Details
java.lang.IllegalArgumentException: Stream has no elements
	at io.quarkus.micrometer.opentelemetry.deployment.common.MetricDataFilter.lastReadingDataPoint(MetricDataFilter.java:236)
	at io.quarkus.micrometer.opentelemetry.deployment.compatibility.MicrometerTimedInterceptorTest.testTimeMethod_UniFailed(MicrometerTimedInterceptorTest.java:201)

⚙️ Maven Tests - JDK 17 Windows

📦 integration-tests/maven

io.quarkus.maven.it.CreateProjectMojoIT.generateNewProjectAndRun - History

  • Condition with Lambda expression in io.quarkus.test.devmode.util.DevModeClient was not fulfilled within 5 minutes. - org.awaitility.core.ConditionTimeoutException
Details
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.test.devmode.util.DevModeClient was not fulfilled within 5 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
	at io.quarkus.test.devmode.util.DevModeClient.getHttpResponse(DevModeClient.java:97)
	at io.quarkus.test.devmode.util.DevModeClient.getHttpResponse(DevModeClient.java:88)

io.quarkus.maven.it.CreateProjectMojoIT.generateNewProjectAndRun - History

  • Condition with Lambda expression in io.quarkus.test.devmode.util.DevModeClient was not fulfilled within 5 minutes. - org.awaitility.core.ConditionTimeoutException
Details
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.test.devmode.util.DevModeClient was not fulfilled within 5 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
	at io.quarkus.test.devmode.util.DevModeClient.getHttpResponse(DevModeClient.java:97)
	at io.quarkus.test.devmode.util.DevModeClient.getHttpResponse(DevModeClient.java:88)

@Sanne Sanne merged commit 043f084 into main Dec 18, 2025
63 of 64 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.31 - main milestone Dec 18, 2025
@dependabot dependabot bot deleted the dependabot/maven/main/io.opentelemetry.instrumentation-opentelemetry-instrumentation-bom-alpha-2.23.0-alpha branch December 18, 2025 21:05
@brunobat
Copy link
Member

Hi @Sanne, we usually don't merge these bot PRs for OTel.
Even if all is good, we also need to update SR Reactive messaging to keep versions in sync. Will handle that.

@brunobat
Copy link
Member

@Sanne
Copy link
Member

Sanne commented Dec 19, 2025

@brunobat ok sorry. Could you disable it then?

@brunobat
Copy link
Member

Sure!

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants