[dependabot]

Bumps io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha from 2.29.0-alpha to 2.33.1-alpha.

Release notes

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

Version 2.33.0

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

📈 Enhancements

• Update the OpenTelemetry SDK version to 1.67.0. (#20598)

🛠️ Bug fixes

• Preserve repeated baggage header values when extracting context through the Java agent's OpenTelemetry API bridge. (#20598)
• Avoid converting lists and maps to strings in Spring Boot declarative configuration. (#20598)
• Improve SQL parsing. (#20864)

🙇 Thank you

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

@​ishg @​jack-berg @​jamesylgan @​laurit @​opentelemetry-pr-dashboard @​safris @​steverao @​trask

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)

... (truncated)

Changelog

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

Changelog

Unreleased

⚠️ Breaking changes

• Apache HttpClient 4.3 library instrumentation no longer automatically emits network.peer.address or network.peer.port inferred from the route target. Use server.address and server.port for logical destination grouping.
• Configured service mappings now emit server.service.name and server.service.namespace, and no longer emit peer.service, service.peer.name, or service.peer.namespace. Rename otel.instrumentation.common.peer-service-mapping to otel.instrumentation.common.server-service-mapping; in YAML, use java.common.server_service_mapping with target instead of peer.
• Rename otel.instrumentation.grpc.{client,server}.request-metadata.{included,excluded} to otel.instrumentation.grpc.{client,server}.request-headers.{included,excluded}.
• Captured gRPC request attributes now use rpc.request.header.<key> instead of rpc.request.metadata.<key>.
• Rename messaging.system to messaging.system.name (aws_sqs becomes aws.sqs) and adopt the system-specific attribute renames from [semantic-conventions #4250](open-telemetry/semantic-conventions#4250). Experimental messaging attributes also lose the messaging. prefix (for example, messaging.kafka.bootstrap.servers becomes kafka.bootstrap.servers).
• AWS Lambda invocation spans now replace alias suffixes in cloud.resource_id with the resolved function version when available.
• AWS Lambda spans now use faas.invocation.id instead of faas.invocation_id for invocation IDs.
• Replace SpringWebfluxClientTelemetry.addFilter(list) and addFilterAndRegisterReactorHook(list) with createFilter() and createFilterAndRegisterReactorHook(), used with WebClient.Builder.filter(...).
• RPC telemetry now uses only the conventions with schema version 1.44.0: rpc.system.name, fully qualified rpc.method, rpc.status_code, and error.type, with updated span names. RPC duration metrics use rpc.client.call.duration and rpc.server.call.duration in seconds. RPC opt-in/preview flags and general.rpc.semconv settings no longer select legacy or dual emission.
• GenAI error type getters now return the final value. Returning null omits error.type; overrides should return error == null ? null : error.getClass().getName() for the exception-class fallback.
• HTTP client and server getters now determine error.type; their returned value, including null, is used as-is.
• RPC attribute getters return the final error.type; returning null omits it even when an exception exists.
• Messaging MessagingAttributesGetter.getErrorType() overrides now provide the final error.type value. Return null to omit it, or return error == null ? null : error.getClass().getName() for exception-class fallback.
• Require R2DBC SPI 1.0 or later.
• Rename the Spark Java instrumentation selector from spark-2.3 to spark-2.4.
• Spring Boot Java agent resource providers move from io.opentelemetry.instrumentation.spring.resources to io.opentelemetry.javaagent.instrumentation.spring.boot.resources. Update class names in otel.java.enabled.resource.providers and otel.java.disabled.resource.providers.
• Spring Rabbit 1.0 is no longer supported. Use the spring-rabbit-1.1 selector; telemetry scope changes from io.opentelemetry.spring-rabbit-1.0 to io.opentelemetry.spring-rabbit-1.1.
• InstrumenterBuilder no longer infers a schema URL from attribute extractors. Call setSchemaUrl() with the schema for the conventions defining the instrumenter's signals; otherwise its telemetry has no schema URL.
• Remove the Spring Boot starter-provided ConfigProperties bean in declarative mode.

... (truncated)

Commits

• See full diff in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha	[>= 2.15.a0, < 2.16]

[ozangunalp]

@dependabot rebase