Bump io.opentelemetry.instrumentation:opentelemetry-grpc-1.6 in /

[dependabot]

Bumps io.opentelemetry.instrumentation:opentelemetry-grpc-1.6 in / from 2.31.1-alpha to 2.32.0-alpha.

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

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-grpc-1.6'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-grpc-1.6's changelog.

Changelog

Unreleased

⚠️ Breaking changes

• RPC and service-peer semantic conventions now require otel.semconv-stability.preview=rpc and otel.semconv-stability.preview=service.peer, respectively (or rpc/dup and service.peer/dup for dual emission). The rpc, rpc/dup, service.peer, and service.peer/dup values in otel.semconv-stability.opt-in no longer select them. For declarative configuration, move these values from general.stability_opt_in_list to java.common.semconv_stability.preview. Default telemetry and explicit general.rpc.semconv configuration are unchanged.
• Micrometer timers and distribution summaries no longer emit separate .max gauge metrics; use the maximum from their histogram instead. Custom meter statistic suffixes are appended after the base name passes through the naming convention (for example, Prometheus mode changes my.meter.count.bytes to my.meter.bytes.count). Remove the deprecated otel.instrumentation.micrometer.histogram-gauges.enabled setting and use otel.instrumentation.micrometer.experimental.histogram-gauges.enabled.
• Servlet principal and Spring Security identity capture now emit user.name and string-array user.roles instead of enduser.id and comma-separated enduser.role. Replace otel.instrumentation.common.enduser.id.enabled and otel.instrumentation.common.enduser.role.enabled with otel.instrumentation.common.user.name.enabled and otel.instrumentation.common.user.roles.enabled. Replace otel.instrumentation.spring-security.enduser.role.granted-authority-prefix with otel.instrumentation.spring-security.user.roles.granted-authority-prefix. The otel.instrumentation.common.enduser.scope.enabled setting and enduser.scope capture are removed. Identity capture remains disabled by default.
• Remove Log4j appender correlation reconstructed from trace-ID, span-ID, and trace-flags strings. For standalone asynchronous logging, configure log4j2.ContextDataInjector=io.opentelemetry.instrumentation.log4j.appender.v2_17.OpenTelemetryAppenderContextDataInjector to carry the full OpenTelemetry context; Java agent correlation remains supported. The appender no longer brings in io.opentelemetry.instrumentation:opentelemetry-log4j-context-data-2.17-autoconfigure transitively; add it separately if Log4j layouts need trace or span IDs. Replace otel.instrumentation.common.logging.trace-id, .span-id, and .trace-flags with .trace-id-key, .span-id-key, and .trace-flags-key, respectively. For declarative configuration, replace java.common.logging.trace_id, span_id, and trace_flags with java.common.logging.trace_id_key, span_id_key, and trace_flags_key.
• Remove otel.instrumentation.grpc.capture-metadata.client.request and otel.instrumentation.grpc.capture-metadata.server.request. Use otel.instrumentation.grpc.client.request-metadata.included and otel.instrumentation.grpc.server.request-metadata.included. For declarative configuration, replace java.grpc.capture_metadata.client.request and java.grpc.capture_metadata.server.request with java.grpc.client.request_metadata.included and java.grpc.server.request_metadata.included.
• Captured messaging header attribute keys now preserve dashes unconditionally; for example,

... (truncated)

Commits

• See full diff in compare view

[bestbeforetoday]

@dependabot rebase

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud