Bump the opentelemetry group with 9 updates

[dependabot]

Bumps the opentelemetry group with 9 updates:

Package	From	To
io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom	2.31.1	2.32.0
io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha	2.31.1-alpha	2.32.0-alpha
io.opentelemetry.instrumentation:opentelemetry-instrumentation-api-incubator	2.31.1-alpha	2.32.0-alpha
io.opentelemetry.javaagent:opentelemetry-javaagent-extension-api	2.31.1-alpha	2.32.0-alpha
io.opentelemetry.javaagent:opentelemetry-javaagent-bootstrap	2.31.1-alpha	2.32.0-alpha
io.opentelemetry.javaagent:opentelemetry-javaagent-tooling	2.31.1-alpha	2.32.0-alpha
io.opentelemetry.contrib:opentelemetry-jfr-connection	1.60.0-alpha	1.61.0-alpha
io.opentelemetry.contrib:opentelemetry-runtime-attach-core	1.60.0-alpha	1.61.0-alpha
io.opentelemetry.instrumentation:gradle-plugins	2.31.1-alpha	2.32.0-alpha

Updates io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom from 2.31.1 to 2.32.0

Release notes

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

Version 2.32.0

This release targets the OpenTelemetry SDK 1.66.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

⚠️ Breaking changes to non-stable APIs

• Remove the deprecated HostIdResource.REGISTRY_QUERY constant. (#19778)
• The ExperimentalJmxMetricHandler SPI now requires implementations to provide getMetricNames(). (#19781)
• Add the required isRequestStreaming(REQUEST) method to GenAiAttributesGetter. (#19879)
• The experimental java.common.messaging.headers/development YAML selector no longer configures header capture. Use java.common.messaging.headers instead. (#20260)

🚫 Deprecations

• Deprecate otel.jmx.target.system in favor of otel.jmx.metrics.experimental.included. (#19783)
• Deprecate otel.instrumentation.elasticsearch.capture-search-query. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. (#19675)
• Deprecate otel.instrumentation.opensearch.capture-search-query. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. Sanitization remains enabled by default and configurable with otel.instrumentation.opensearch.query-sanitization.enabled. (#19837)
• Deprecate otel.jmx.enabled in favor of otel.instrumentation.jmx.enabled to align with other instrumentation enablement properties. (#19945)
• Deprecate automatic rewriting of VirtualField.find(Class, Class) calls in inlined javaagent advice. Instead, look up the VirtualField once and store it in a helper class's static final field. The find method itself remains supported. (#19980)
• Deprecate the Elasticsearch REST library instrumentation. Use the Elasticsearch Java API Client's native OpenTelemetry support, or the Java agent for direct RestClient usage. Java agent instrumentation is unaffected. (#19995)
• Deprecate otel.instrumentation.messaging.experimental.receive-telemetry.enabled in favor of otel.instrumentation.common.messaging.experimental.receive-telemetry.enabled. For headers, replace otel.instrumentation.messaging.experimental.headers.included and .excluded with otel.instrumentation.common.messaging.headers.included and .excluded. Also deprecate otel.instrumentation.messaging.experimental.capture-headers in favor of otel.instrumentation.common.messaging.headers.included. Stable selectors take precedence per leaf. (#20060, #20260)
• Deprecate the .included / .excluded properties under otel.instrumentation.log4j-appender.experimental.map-message-attributes, otel.instrumentation.logback-appender.experimental.key-value-pair-attributes, otel.instrumentation.logback-appender.experimental.logstash-marker-attributes, and otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes in favor of the stable and unified otel.instrumentation.common.logging.structured-attributes.included / .excluded. (#20066)
• Deprecate otel.instrumentation.couchbase.experimental-span-attributes in favor of otel.instrumentation.couchbase.emit-experimental-telemetry, a broader name for experimental attributes and internal spans from the underlying Couchbase client. (#20117)
• Deprecate otel.traces.sampler=linksbased_parentbased_always_on with no replacement and declarative rule_based_routing in favor of the SDK incubator composite/development rule_based sampler, whose configuration and matching behavior differ. (#20249)
• Promote controller and view telemetry configuration to the stable properties otel.instrumentation.common.controller-telemetry.enabled and otel.instrumentation.common.view-telemetry.enabled, deprecating otel.instrumentation.common.experimental.controller-telemetry.enabled and otel.instrumentation.common.experimental.view-telemetry.enabled. (#20258)
• Promote Java agent span suppression configuration to the stable property otel.instrumentation.common.span-suppression-strategy, deprecating otel.instrumentation.experimental.span-suppression-strategy. (#20259)
• Deprecate otel.instrumentation.oshi.experimental-metrics.enabled, ProcessMetrics, and its registerObservers(...) methods in favor of jvm.memory.used and jvm.cpu.time. (#20323)
• Deprecate SystemMetrics.registerObservers(Meter) in the OSHI library instrumentation in favor of SystemMetrics.registerObservers(OpenTelemetry). (#20263)
• In declarative configuration YAML, deprecate dotted selectors in the distribution.javaagent.instrumentation.enabled and .disabled lists. Use reactor_3_1 instead of reactor_3.1. Flat-property names such as otel.instrumentation.reactor-3.1.enabled are unchanged. (#20326)

🌟 New javaagent instrumentation

• Add Redisson database connection pool metrics for versions 2.3.0 through 3.25. (#19152, #19634)
• Add Java agent instrumentation for Pekko remoting so trace context propagates across remote calls. (#19823)

📈 Enhancements

• Expand the upcoming 3.0 database semantic conventions behind otel.semconv-stability.opt-in=database, including configured server targets and span names, endpoint validation, network-peer attributes, Redis namespaces, operation names, error types, query text, and connection pool metric names and database identity for Cassandra, ClickHouse, Couchbase, Elasticsearch, Geode, HBase, JDBC, Redis clients, MongoDB, OpenSearch, R2DBC, Spymemcached, and Vert.x. (#19728, #19747, #19749, #19753, #19757, #19795, #19830, #19831, #19832, #19834, #19838, #19839, #19844, #19845, #19846, #19848, #19850, #19864, #19868, #19872, #19877, #19883, #19901, #19902, #19903, #19904, #19981, #19983, #19986, #19988, #20008, #20011, #20015, #20017, #20041, #20065, #20068, #20070, #20071, #20072, #20073, #20074, #20075, #20076, #20077, #20078, #20080, #20082, #20084, #20086, #20089, #20105)
• Expand the upcoming 3.0 messaging semantic conventions behind otel.semconv-stability.opt-in=messaging, including operation-based spans, client and process metrics, per-message batch creation and propagation, consistent timestamps, durable subscription names, and duplicate processing suppression for Camel, Kafka Connect, JMS, SQS, and RocketMQ. (#19483, #19485, #19503, #19517, #19915, #20045, #20067, #20144)
• Kafka spans and metrics now include messaging.kafka.cluster.id once cluster metadata is resolved. (#18978)
• Add SQL database attributes to AWS SDK v2 RDS Data API ExecuteStatement and BatchExecuteStatement spans. (#19259)
• Add WARNING logs for invalid or empty extension locations and failed extension JAR loads, plus FINE logs for successfully loaded extension JARs. (#19584)
• The JMX metrics library now includes the experimental Kafka broker metrics target. (#19722)
• Update the descriptions of kafka.connect.connector.status and kafka.connect.task.status to omit the listed supported state values. (#19724)
• Geode database client spans now include server.address and server.port when the region's pool has exactly one configured server. (#19748)
• Add exception-log support for HBase database clients, SofaRPC clients and servers, and GWT RPC with otel.semconv.exception.signal.preview=logs. (#19750, #20253, #20254)
• Add server.address and server.port attributes to Couchbase database spans. (#19758)
• Add metric-name filtering for JMX metrics with otel.jmx.metrics.included and otel.jmx.metrics.excluded, or JmxTelemetryBuilder.setMetrics(IncludeExclude) in the library. (#19782)
• RabbitMQ spans now include messaging.rabbitmq.vhost.name and messaging.rabbitmq.cluster.name when otel.instrumentation.rabbitmq.experimental-span-attributes=true. (#19822)
• JMX metric creation messages are now logged at FINE instead of INFO, reducing default log noise. (#19825)

... (truncated)

Changelog

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

Version 2.32.0 (2026-10-03)

This release targets the OpenTelemetry SDK 1.66.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

⚠️ Breaking changes to non-stable APIs

• Remove the deprecated HostIdResource.REGISTRY_QUERY constant. (#19778)
• The ExperimentalJmxMetricHandler SPI now requires implementations to provide getMetricNames(). (#19781)
• Add the required isRequestStreaming(REQUEST) method to GenAiAttributesGetter. (#19879)
• The experimental java.common.messaging.headers/development YAML selector no longer configures header capture. Use java.common.messaging.headers instead. (#20260)

🚫 Deprecations

• Deprecate otel.jmx.target.system in favor of otel.jmx.metrics.experimental.included. (#19783)
• Deprecate otel.instrumentation.elasticsearch.capture-search-query. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. (#19675)
• Deprecate otel.instrumentation.opensearch.capture-search-query. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. Sanitization remains enabled by default and configurable with otel.instrumentation.opensearch.query-sanitization.enabled. (#19837)
• Deprecate otel.jmx.enabled in favor of otel.instrumentation.jmx.enabled to align with other instrumentation enablement properties. (#19945)
• Deprecate automatic rewriting of VirtualField.find(Class, Class) calls in inlined javaagent advice. Instead, look up the VirtualField once and store it in a helper class's static final field. The find method itself remains supported. (#19980)
• Deprecate the Elasticsearch REST library instrumentation. Use the Elasticsearch Java API Client's native OpenTelemetry support, or the Java agent for direct RestClient usage. Java agent instrumentation is unaffected. (#19995)
• Deprecate otel.instrumentation.messaging.experimental.receive-telemetry.enabled in favor of otel.instrumentation.common.messaging.experimental.receive-telemetry.enabled. For headers, replace otel.instrumentation.messaging.experimental.headers.included and .excluded with otel.instrumentation.common.messaging.headers.included and .excluded. Also deprecate otel.instrumentation.messaging.experimental.capture-headers in favor of otel.instrumentation.common.messaging.headers.included. Stable selectors take precedence per leaf.

... (truncated)

Commits

• 1b8644f [release/v2.32.x] Prepare release 2.32.0 (#20364)
• 9eaf312 Draft release notes (#20347)
• 9f5c507 Gate DBCP pool name retention on stable database semantic conventions (#20361)
• 50f8bad Restore Renovate Java updates and fix Weaver digest pinning (#20360)
• 5eea491 Align v3-preview javaagent enablement selectors with module identities (#20305)
• 647a9c3 Comment out regex manager from renovate weekly updates (#20341)
• 4f9429c Update pinned latest dep versions (#20349)
• 12afa2c Handle unavailable references when drafting release notes (#20343)
• a401278 Run native tests only on GraalVM 25 LTS (#20332)
• a3a0fca chore(deps): update jdx/mise-action action to v5 (#20316)
• Additional commits viewable in compare view

Updates io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha from 2.31.1-alpha to 2.32.0-alpha

Release notes

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

Version 2.31.1

This release targets the OpenTelemetry SDK 1.65.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

🛠️ Bug fixes

• Restore stable semantic convention APIs to the compile classpaths of the Spring Boot autoconfigure and starter artifacts. (#19754)

Changelog

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

Changelog

Unreleased

⚠️ Breaking changes

• Runtime telemetry metrics and package-emitter events now always use the io.opentelemetry.runtime-telemetry instrumentation scope. Update views, dashboards, and filters that match io.opentelemetry.runtime-telemetry-java8 or io.opentelemetry.runtime-telemetry-java17.
• JMX jvm.gc.duration metrics always include jvm.gc.cause. Remove otel.instrumentation.runtime-telemetry.capture-gc-cause; GC cause is no longer configurable.
• Remove the deprecated runtime telemetry configuration properties and their declarative forms:
  • Replace otel.instrumentation.runtime-telemetry.emit-experimental-telemetry with otel.instrumentation.runtime-telemetry.emit-experimental-metrics.
  • Replace otel.instrumentation.runtime-telemetry.package-emitter.* with otel.instrumentation.runtime-telemetry.experimental.package-emitter.*.
  • Replace otel.instrumentation.runtime-telemetry-java17.enabled with otel.instrumentation.runtime-telemetry.emit-experimental-jfr-metrics.
  • Replace otel.instrumentation.runtime-telemetry-java17.enable-all with otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included=*.
  • Replace otel.instrumentation.runtime-telemetry.experimental.prefer-jfr with explicit metric selections in otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included.
• Remove the legacy JFR metric name jvm.cpu.limit. Use jvm.cpu.count instead.
• Remove the retired flat settings otel.instrumentation.common.db-statement-sanitizer.enabled and otel.instrumentation.<module>.statement-sanitizer.enabled; use otel.instrumentation.common.db.query-sanitization.enabled and otel.instrumentation.<module>.query-sanitization.enabled instead. Replace java.common.database.sqlcommenter/development.enabled with java.common.db.sqlcommenter/development.enabled; the flat setting otel.instrumentation.common.db.experimental.sqlcommenter.enabled remains supported.
• Apache Wicket resource requests now always use the resource reference class name for http.route and the HTTP server span name, instead of the servlet wildcard route.
• The Java agent, Spring Boot setup, and standalone appenders now capture structured log attributes from Log4j MapMessage entries, SLF4J key-value pairs, Logback Logstash markers, and Logstash structured arguments by default. Replace the former flat settings for Log4j MapMessage (otel.instrumentation.log4j-appender.experimental.capture-map-message-attributes), Logback key/value pairs (otel.instrumentation.logback-appender.experimental.capture-key-value-pair-attributes), Logstash markers (otel.instrumentation.logback-appender.experimental.capture-logstash-marker-attributes), and structured arguments (otel.instrumentation.logback-appender.experimental.capture-logstash-structured-arguments) with the common otel.instrumentation.common.logging.structured-attributes.included and otel.instrumentation.common.logging.structured-attributes.excluded selectors. Exclusions take precedence, and * excludes all structured attributes. The source-specific .included and .excluded selectors (otel.instrumentation.log4j-appender.experimental.map-message-attributes.*, otel.instrumentation.logback-appender.experimental.key-value-pair-attributes.*, otel.instrumentation.logback-appender.experimental.logstash-marker-attributes.*, and otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes.*) were removed and are now ignored, so migrate them to the common selectors to keep filtering.

... (truncated)

Commits

• See full diff in compare view

Updates io.opentelemetry.instrumentation:opentelemetry-instrumentation-api-incubator from 2.31.1-alpha to 2.32.0-alpha

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-instrumentation-api-incubator's releases.

Version 2.31.1

This release targets the OpenTelemetry SDK 1.65.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

🛠️ Bug fixes

• Restore stable semantic convention APIs to the compile classpaths of the Spring Boot autoconfigure and starter artifacts. (#19754)

Changelog

Sourced from io.opentelemetry.instrumentation:opentelemetry-instrumentation-api-incubator's changelog.

Changelog

Unreleased

⚠️ Breaking changes

• Runtime telemetry metrics and package-emitter events now always use the io.opentelemetry.runtime-telemetry instrumentation scope. Update views, dashboards, and filters that match io.opentelemetry.runtime-telemetry-java8 or io.opentelemetry.runtime-telemetry-java17.
• JMX jvm.gc.duration metrics always include jvm.gc.cause. Remove otel.instrumentation.runtime-telemetry.capture-gc-cause; GC cause is no longer configurable.
• Remove the deprecated runtime telemetry configuration properties and their declarative forms:
  • Replace otel.instrumentation.runtime-telemetry.emit-experimental-telemetry with otel.instrumentation.runtime-telemetry.emit-experimental-metrics.
  • Replace otel.instrumentation.runtime-telemetry.package-emitter.* with otel.instrumentation.runtime-telemetry.experimental.package-emitter.*.
  • Replace otel.instrumentation.runtime-telemetry-java17.enabled with otel.instrumentation.runtime-telemetry.emit-experimental-jfr-metrics.
  • Replace otel.instrumentation.runtime-telemetry-java17.enable-all with otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included=*.
  • Replace otel.instrumentation.runtime-telemetry.experimental.prefer-jfr with explicit metric selections in otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included.
• Remove the legacy JFR metric name jvm.cpu.limit. Use jvm.cpu.count instead.
• Remove the retired flat settings otel.instrumentation.common.db-statement-sanitizer.enabled and otel.instrumentation.<module>.statement-sanitizer.enabled; use otel.instrumentation.common.db.query-sanitization.enabled and otel.instrumentation.<module>.query-sanitization.enabled instead. Replace java.common.database.sqlcommenter/development.enabled with java.common.db.sqlcommenter/development.enabled; the flat setting otel.instrumentation.common.db.experimental.sqlcommenter.enabled remains supported.
• Apache Wicket resource requests now always use the resource reference class name for http.route and the HTTP server span name, instead of the servlet wildcard route.
• The Java agent, Spring Boot setup, and standalone appenders now capture structured log attributes from Log4j MapMessage entries, SLF4J key-value pairs, Logback Logstash markers, and Logstash structured arguments by default. Replace the former flat settings for Log4j MapMessage (otel.instrumentation.log4j-appender.experimental.capture-map-message-attributes), Logback key/value pairs (otel.instrumentation.logback-appender.experimental.capture-key-value-pair-attributes), Logstash markers (otel.instrumentation.logback-appender.experimental.capture-logstash-marker-attributes), and structured arguments (otel.instrumentation.logback-appender.experimental.capture-logstash-structured-arguments) with the common otel.instrumentation.common.logging.structured-attributes.included and otel.instrumentation.common.logging.structured-attributes.excluded selectors. Exclusions take precedence, and * excludes all structured attributes. The source-specific .included and .excluded selectors (otel.instrumentation.log4j-appender.experimental.map-message-attributes.*, otel.instrumentation.logback-appender.experimental.key-value-pair-attributes.*, otel.instrumentation.logback-appender.experimental.logstash-marker-attributes.*, and otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes.*) were removed and are now ignored, so migrate them to the common selectors to keep filtering.

... (truncated)

Commits

• See full diff in compare view

Updates io.opentelemetry.javaagent:opentelemetry-javaagent-extension-api from 2.31.1-alpha to 2.32.0-alpha

Release notes

Sourced from io.opentelemetry.javaagent:opentelemetry-javaagent-extension-api's releases.

Version 2.31.1

This release targets the OpenTelemetry SDK 1.65.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

🛠️ Bug fixes

• Restore stable semantic convention APIs to the compile classpaths of the Spring Boot autoconfigure and starter artifacts. (#19754)

Changelog

Sourced from io.opentelemetry.javaagent:opentelemetry-javaagent-extension-api's changelog.

Changelog

Unreleased

⚠️ Breaking changes

• Runtime telemetry metrics and package-emitter events now always use the io.opentelemetry.runtime-telemetry instrumentation scope. Update views, dashboards, and filters that match io.opentelemetry.runtime-telemetry-java8 or io.opentelemetry.runtime-telemetry-java17.
• JMX jvm.gc.duration metrics always include jvm.gc.cause. Remove otel.instrumentation.runtime-telemetry.capture-gc-cause; GC cause is no longer configurable.
• Remove the deprecated runtime telemetry configuration properties and their declarative forms:
  • Replace otel.instrumentation.runtime-telemetry.emit-experimental-telemetry with otel.instrumentation.runtime-telemetry.emit-experimental-metrics.
  • Replace otel.instrumentation.runtime-telemetry.package-emitter.* with otel.instrumentation.runtime-telemetry.experimental.package-emitter.*.
  • Replace otel.instrumentation.runtime-telemetry-java17.enabled with otel.instrumentation.runtime-telemetry.emit-experimental-jfr-metrics.
  • Replace otel.instrumentation.runtime-telemetry-java17.enable-all with otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included=*.
  • Replace otel.instrumentation.runtime-telemetry.experimental.prefer-jfr with explicit metric selections in otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included.
• Remove the legacy JFR metric name jvm.cpu.limit. Use jvm.cpu.count instead.
• Remove the retired flat settings otel.instrumentation.common.db-statement-sanitizer.enabled and otel.instrumentation.<module>.statement-sanitizer.enabled; use otel.instrumentation.common.db.query-sanitization.enabled and otel.instrumentation.<module>.query-sanitization.enabled instead. Replace java.common.database.sqlcommenter/development.enabled with java.common.db.sqlcommenter/development.enabled; the flat setting otel.instrumentation.common.db.experimental.sqlcommenter.enabled remains supported.
• Apache Wicket resource requests now always use the resource reference class name for http.route and the HTTP server span name, instead of the servlet wildcard route.
• The Java agent, Spring Boot setup, and standalone appenders now capture structured log attributes from Log4j MapMessage entries, SLF4J key-value pairs, Logback Logstash markers, and Logstash structured arguments by default. Replace the former flat settings for Log4j MapMessage (otel.instrumentation.log4j-appender.experimental.capture-map-message-attributes), Logback key/value pairs (otel.instrumentation.logback-appender.experimental.capture-key-value-pair-attributes), Logstash markers (otel.instrumentation.logback-appender.experimental.capture-logstash-marker-attributes), and structured arguments (otel.instrumentation.logback-appender.experimental.capture-logstash-structured-arguments) with the common otel.instrumentation.common.logging.structured-attributes.included and otel.instrumentation.common.logging.structured-attributes.excluded selectors. Exclusions take precedence, and * excludes all structured attributes. The source-specific .included and .excluded selectors (otel.instrumentation.log4j-appender.experimental.map-message-attributes.*, otel.instrumentation.logback-appender.experimental.key-value-pair-attributes.*, otel.instrumentation.logback-appender.experimental.logstash-marker-attributes.*, and otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes.*) were removed and are now ignored, so migrate them to the common selectors to keep filtering.

... (truncated)

Commits

• See full diff in compare view

Updates io.opentelemetry.javaagent:opentelemetry-javaagent-bootstrap from 2.31.1-alpha to 2.32.0-alpha

Release notes

Sourced from io.opentelemetry.javaagent:opentelemetry-javaagent-bootstrap's releases.

Version 2.31.1

This release targets the OpenTelemetry SDK 1.65.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

🛠️ Bug fixes

• Restore stable semantic convention APIs to the compile classpaths of the Spring Boot autoconfigure and starter artifacts. (#19754)

Changelog

Sourced from io.opentelemetry.javaagent:opentelemetry-javaagent-bootstrap's changelog.

Changelog

Unreleased

⚠️ Breaking changes

• Runtime telemetry metrics and package-emitter events now always use the io.opentelemetry.runtime-telemetry instrumentation scope. Update views, dashboards, and filters that match io.opentelemetry.runtime-telemetry-java8 or io.opentelemetry.runtime-telemetry-java17.
• JMX jvm.gc.duration metrics always include jvm.gc.cause. Remove otel.instrumentation.runtime-telemetry.capture-gc-cause; GC cause is no longer configurable.
• Remove the deprecated runtime telemetry configuration properties and their declarative forms:
  • Replace otel.instrumentation.runtime-telemetry.emit-experimental-telemetry with otel.instrumentation.runtime-telemetry.emit-experimental-metrics.
  • Replace otel.instrumentation.runtime-telemetry.package-emitter.* with otel.instrumentation.runtime-telemetry.experimental.package-emitter.*.
  • Replace otel.instrumentation.runtime-telemetry-java17.enabled with otel.instrumentation.runtime-telemetry.emit-experimental-jfr-metrics.
  • Replace otel.instrumentation.runtime-telemetry-java17.enable-all with otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included=*.
  • Replace otel.instrumentation.runtime-telemetry.experimental.prefer-jfr with explicit metric selections in otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included.
• Remove the legacy JFR metric name jvm.cpu.limit. Use jvm.cpu.count instead.
• Remove the retired flat settings otel.instrumentation.common.db-statement-sanitizer.enabled and otel.instrumentation.<module>.statement-sanitizer.enabled; use otel.instrumentation.common.db.query-sanitization.enabled and otel.instrumentation.<module>.query-sanitization.enabled instead. Replace java.common.database.sqlcommenter/development.enabled with java.common.db.sqlcommenter/development.enabled; the flat setting otel.instrumentation.common.db.experimental.sqlcommenter.enabled remains supported.
• Apache Wicket resource requests now always use the resource reference class name for http.route and the HTTP server span name, instead of the servlet wildcard route.
• The Java agent, Spring Boot setup, and standalone appenders now capture structured log attributes from Log4j MapMessage entries, SLF4J key-value pairs, Logback Logstash markers, and Logstash structured arguments by default. Replace the former flat settings for Log4j MapMessage (otel.instrumentation.log4j-appender.experimental.capture-map-message-attributes), Logback key/value pairs (otel.instrumentation.logback-appender.experimental.capture-key-value-pair-attributes), Logstash markers (otel.instrumentation.logback-appender.experimental.capture-logstash-marker-attributes), and structured arguments (otel.instrumentation.logback-appender.experimental.capture-logstash-structured-arguments) with the common otel.instrumentation.common.logging.structured-attributes.included and otel.instrumentation.common.logging.structured-attributes.excluded selectors. Exclusions take precedence, and * excludes all structured attributes. The source-specific .included and .excluded selectors (otel.instrumentation.log4j-appender.experimental.map-message-attributes.*, otel.instrumentation.logback-appender.experimental.key-value-pair-attributes.*, otel.instrumentation.logback-appender.experimental.logstash-marker-attributes.*, and otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes.*) were removed and are now ignored, so migrate them to the common selectors to keep filtering.

... (truncated)

Commits

• See full diff in compare view

Updates io.opentelemetry.javaagent:opentelemetry-javaagent-tooling from 2.31.1-alpha to 2.32.0-alpha

Release notes

Sourced from io.opentelemetry.javaagent:opentelemetry-javaagent-tooling's releases.

Version 2.31.1

This release targets the OpenTelemetry SDK 1.65.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

🛠️ Bug fixes

• Restore stable semantic convention APIs to the compile classpaths of the Spring Boot autoconfigure and starter artifacts. (#19754)

Changelog

Sourced from io.opentelemetry.javaagent:opentelemetry-javaagent-tooling's changelog.

Changelog

Unreleased

⚠️ Breaking changes

• Runtime telemetry metrics and package-emitter events now always use the io.opentelemetry.runtime-telemetry instrumentation scope. Update views, dashboards, and filters that match io.opentelemetry.runtime-telemetry-java8 or io.opentelemetry.runtime-telemetry-java17.
• JMX jvm.gc.duration metrics always include jvm.gc.cause. Remove otel.instrumentation.runtime-telemetry.capture-gc-cause; GC cause is no longer configurable.
• Remove the deprecated runtime telemetry configuration properties and their declarative forms:
  • Replace otel.instrumentation.runtime-telemetry.emit-experimental-telemetry with otel.instrumentation.runtime-telemetry.emit-experimental-metrics.
  • Replace otel.instrumentation.runtime-telemetry.package-emitter.* with otel.instrumentation.runtime-telemetry.experimental.package-emitter.*.
  • Replace otel.instrumentation.runtime-telemetry-java17.enabled with otel.instrumentation.runtime-telemetry.emit-experimental-jfr-metrics.
  • Replace otel.instrumentation.runtime-telemetry-java17.enable-all with otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included=*.
  • Replace otel.instrumentation.runtime-telemetry.experimental.prefer-jfr with explicit metric selections in otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included.
• Remove the legacy JFR metric name jvm.cpu.limit. Use jvm.cpu.count instead.
• Remove the retired flat settings otel.instrumentation.common.db-statement-sanitizer.enabled and otel.instrumentation.<module>.statement-sanitizer.enabled; use otel.instrumentation.common.db.query-sanitization.enabled and otel.instrumentation.<module>.query-sanitization.enabled instead. Replace java.common.database.sqlcommenter/development.enabled with java.common.db.sqlcommenter/development.enabled; the flat setting otel.instrumentation.common.db.experimental.sqlcommenter.enabled remains supported.
• Apache Wicket resource requests now always use the resource reference class name for http.route and the HTTP server span name, instead of the servlet wildcard route.
• The Java agent, Spring Boot setup, and standalone appenders now capture structured log attributes from Log4j MapMessage entries, SLF4J key-value pairs, Logback Logstash markers, and Logstash structured arguments by default. Replace the former flat settings for Log4j MapMessage (otel.instrumentation.log4j-appender.experimental.capture-map-message-attributes), Logback key/value pairs (otel.instrumentation.logback-appender.experimental.capture-key-value-pair-attributes), Logstash markers (otel.instrumentation.logback-appender.experimental.capture-logstash-marker-attributes), and structured arguments (otel.instrumentation.logback-appender.experimental.capture-logstash-structured-arguments) with the common otel.instrumentation.common.logging.structured-attributes.included and otel.instrumentation.common.logging.structured-attributes.excluded selectors. Exclusions take precedence, and * excludes all structured attributes. The source-specific .included and .excluded selectors (otel.instrumentation.log4j-appender.experimental.map-message-attributes.*, otel.instrumentation.logback-appender.experimental.key-value-pair-attributes.*, otel.instrumentation.logback-appender.experimental.logstash-marker-attributes.*, and otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes.*) were removed and are now ignored, so migrate them to the common selectors to keep filtering.

... (truncated)

Commits

• See full diff in compare view

Updates io.opentelemetry.instrumentation:opentelemetry-instrumentation-api-incubator from 2.31.1-alpha to 2.32.0-alpha

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-instrumentation-api-incubator's releases.

Version 2.31.1

This release targets the OpenTelemetry SDK 1.65.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

🛠️ Bug fixes

• Restore stable semantic convention APIs to the compile classpaths of the Spring Boot autoconfigure and starter artifacts. (#19754)

Changelog

Sourced from io.opentelemetry.instrumentation:opentelemetry-instrumentation-api-incubator's changelog.

Changelog

Unreleased

⚠️ Breaking changes

• Runtime telemetry metrics and package-emitter events now always use the io.opentelemetry.runtime-telemetry instrumentation scope. Update views, dashboards, and filters that match io.opentelemetry.runtime-telemetry-java8 or io.opentelemetry.runtime-telemetry-java17.
• JMX jvm.gc.duration metrics always include jvm.gc.cause. Remove otel.instrumentation.runtime-telemetry.capture-gc-cause; GC cause is no longer configurable.
• Remove the deprecated runtime telemetry configuration properties and their declarative forms:
  • Replace otel.instrumentation.runtime-telemetry.emit-experimental-telemetry with otel.instrumentation.runtime-telemetry.emit-experimental-metrics.
  • Replace otel.instrumentation.runtime-telemetry.package-emitter.* with otel.instrumentation.runtime-telemetry.experimental.package-emitter.*.
  • Replace otel.instrumentation.runtime-telemetry-java17.enabled with otel.instrumentation.runtime-telemetry.emit-experimental-jfr-metrics.
  • Replace otel.instrumentation.runtime-telemetry-java17.enable-all with otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included=*.
  • Replace otel.instrumentation.runtime-telemetry.experimental.prefer-jfr with explicit metric selections in otel.instrumentation.runtime-telemetry.experimental.jfr-metrics.included.
• Remove the legacy JFR metric name jvm.cpu.limit. Use jvm.cpu.count instead.
• Remove the retired flat settings otel.instrumentation.common.db-statement-sanitizer.enabled and otel.instrumentation.<module>.statement-sanitizer.enabled; use otel.instrumentation.common.db.query-sanitization.enabled and otel.instrumentation.<module>.query-sanitization.enabled instead. Replace java.common.database.sqlcommenter/development.enabled with java.common.db.sqlcommenter/development.enabled; the flat setting otel.instrumentation.common.db.experimental.sqlcommenter.enabled remains supported.
• Apache Wicket resource requests now always use the resource reference class name for http.route and the HTTP server span name, instead of the servlet wildcard route.
• The Java agent, Spring Boot setup, and standalone appenders now capture structured log attributes from Log4j MapMessage entries, SLF4J key-value pairs, Logback Logstash markers, and Logstash structured arguments by default. Replace the former flat settings for Log4j MapMessage (otel.instrumentation.log4j-appender.experimental.capture-map-message-attributes), Logback key/value pairs (otel.instrumentation.logback-appender.experimental.capture-key-value-pair-attributes), Logstash markers (otel.instrumentation.logback-appender.experimental.capture-logstash-marker-attributes), and structured arguments (otel.instrumentation.logback-appender.experimental.capture-logstash-structured-arguments) with the common otel.instrumentation.common.logging.structured-attributes.included and otel.instrumentation.common.logging.structured-attributes.excluded selectors. Exclusions take precedence, and * excludes all structured attributes. The source-specific .included and .excluded selectors (otel.instrumentation.log4j-appender.experimental.map-message-attributes.*, otel.instrumentation.logback-appender.experimental.key-value-pair-attributes.*, otel.instrumentation.logback-appender.experimental.logstash-marker-attributes.*, and otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes.*) were removed and are now ignored, so migrate them to the common selectors to keep filtering.

... (truncated)

Commits

• See full diff in compare view

Updates io.opentelemetry.javaagent:opentelemetry-javaagent-extension-api from 2.31.1-alpha to 2.32.0-alpha

Release notes

Sourced from io.opentelemetry.javaagent:opentelemetry-javaagent-extension-api's releases.

Version 2.31.1

This release targets the OpenTelemetry SDK 1.65.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

🛠️ Bug fixes

• Restore stable semantic convention APIs to the compile classpaths of the Spring Boot autoconfigure and starter artifacts. (#19754)

Changelog

Sourced from io.opentelemetry.javaagent:opentelemetry-javaagent-extension-api's changelog.

Changelog

Unreleased

⚠️ Breaking changes

• Runtime telemetry metrics and package-emitter events now always use the io.openteleme...

  Description has been truncated