deps: update opentelemetry.version to v1.60.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.opentelemetry:opentelemetry-sdk-testing	1.59.0 → 1.60.0
io.opentelemetry:opentelemetry-sdk-trace	1.59.0 → 1.60.0
io.opentelemetry:opentelemetry-sdk-metrics	1.59.0 → 1.60.0
io.opentelemetry:opentelemetry-sdk	1.59.0 → 1.60.0

---

Release Notes

open-telemetry/opentelemetry-java (io.opentelemetry:opentelemetry-sdk-testing)

v1.60.0

API

• Support W3C trace context random flag
  (#​8012)
• Clarify that SpanBuilder.setAttribute allows null values
  (#​8072)

Incubating

• Implement environment variable context propagation carriers
  (#​8074)
• Deprecate ExtendedAttributes, ExtendedAttributeKey, ExtendedAttributeType,
  ExtendedAttributesBuilder
  (#​8060)
• Deprecate peerServiceMapping accessor from InstrumentationConfigUtil
  (#​8088)

SDK

Traces

• Disable warning when using TraceIdRatioBasedSampler as root sampler
  (#​8065)
• User-supplied attributes take precedence over exception-derived attributes
  (#​7993)
• Exclude META-INF/maven from traces SDK shaded dependencies
  (#​8096)
• Fix inverted condition in LegacySpanProcessorInstrumentation#finishSpans
  (#​8145)

Metrics

• Split out cumulative vs. delta storage
  (#​8015)
• Add metrics for PeriodicMetricReader
  (#​8038)
• Allow configuring min/max in histograms
  (#​8095)
• Remove deprecated otel.experimental.metrics.cardinality.limit property
  (#​8124)
• BREAKING bug fix: GlobUtil and IncludePatternMatching, used in views and declarative
  config matching, previously were inconsistent in case sensitivity. If a glob char (* or ?) was
  present, it was evaluated with case sensitivity. If no glob chars were present, it was evaluated
  with case insensitivity. Now, all are consistently evaluated with case sensitivity.
  (#​8152)

Logs

• Stabilize LogRecordBuilder.setException
  (#​8089)
• Clarify setTimestamp javadoc for event timestamp behavior
  (#​8104)

Exporters

• OTLP: Fix marshaling for empty string attributes
  (#​8014)
• Prometheus: Update Prometheus client to 1.5.0
  (#​8080)
• OTLP: Serialize exponential histogram sum as optional double
  (#​8107)
• OTLP: Use KeyManagerFactory.getDefaultAlgorithm() in TlsUtil.keyManager()
  (#​8122)
• OTLP: Ensure proto serializer idCache is cleared when exception is thrown
  (#​8147)

Extensions

• Autoconfigure: Decode plus sign in resource attributes
  (#​8059)
• Declarative config: update to 1.0 schema
  (#​8123)
• Declarative config: add support for setting schema URL
  (#​8028)
• Declarative config: add version mismatch warning
  (#​8069)
• Declarative config: cache component providers in DeclarativeConfigContext
  (#​8070)
• Declarative config: add system property substitution
  (#​8073)
• Declarative config: add exporter customizers
  (#​8081)
• Declarative config: add support for setting internal telemetry version
  (#​8045)
• Deprecate View File Configuration mechanism
  (#​8133)
• Autoconfigure: add property to allow autoconfiguration of SDK telemetry version
  (#​8037)
• Jaeger remote sampler: refactor to leverage senders
  (#​8046)
• Declarative config: document ObjectMapper config
  (#​8075)
• Declarative config: Remove unchecked warning
  (#​8090)

Project tooling

• Add architecture test to detect usage of shared internal code
  (#​6978)
• Replace Xlint deprecation check with custom error-prone check
  (#​8061)
• Enable error-prone's UnnecessarilyFullyQualified check
  (#​8078)
• Small refactoring to make safety clearer
  (#​8083)
• Rework span record benchmark and publish results
  (#​8031)
• Add LogRecordBenchmark
  (#​8106,
  #​8117)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dpebot]

/gcbrun

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the OpenTelemetry dependency version to 1.60.0. This upgrade incorporates a range of new features, bug fixes, and deprecations across the OpenTelemetry API, SDK components (Traces, Metrics, Logs), Exporters, and Extensions. A notable change is a breaking modification to case sensitivity in metric view matching, alongside significant enhancements to declarative configuration capabilities.

Highlights

• Dependency Update: Updated the opentelemetry.version from 1.59.0 to 1.60.0 in benchmarks/pom.xml.
• Breaking Change: Introduced a breaking change in metric views and declarative config matching, where GlobUtil and IncludePatternMatching are now consistently evaluated with case sensitivity, unlike previous inconsistent behavior.
• API Enhancements: Added support for the W3C trace context random flag and clarified that SpanBuilder.setAttribute allows null values.
• SDK Metrics Improvements: Implemented a split between cumulative and delta storage, added metrics for PeriodicMetricReader, and allowed configuration of min/max values in histograms.
• Declarative Configuration Updates: Updated declarative configuration to the 1.0 schema, including support for setting schema URLs, version mismatch warnings, system property substitution, and exporter customizers.
• Deprecations: Deprecated ExtendedAttributes, ExtendedAttributeKey, ExtendedAttributeType, ExtendedAttributesBuilder, peerServiceMapping accessor, and the View File Configuration mechanism.

Changelog

• benchmarks/pom.xml
  • Updated opentelemetry.version from 1.59.0 to 1.60.0.

Activity

• Automatically created by Renovate Bot to update the opentelemetry.version dependency.
• Automerge is currently disabled, requiring manual review and merging.
• Configured for automatic rebasing if conflicts arise or upon manual trigger.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This PR, generated by Renovate, updates the opentelemetry.version property in benchmarks/pom.xml to 1.60.0. While this update itself seems fine and the breaking changes in this OpenTelemetry version are unlikely to affect this project, I've noticed a potential issue with how OpenTelemetry dependencies are managed in this module. There's a risk of version mismatch between different OpenTelemetry artifacts, which could lead to runtime issues. I've added a comment with a suggestion to improve this by using the OpenTelemetry BOM for consistent version management.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

While this version update is correct, it highlights an underlying issue with how OpenTelemetry dependencies are managed in this pom.xml.

Some dependencies like opentelemetry-api (line 43) inherit their version from parent POMs, while others like opentelemetry-sdk (line 67) use this explicit ${opentelemetry.version} property. This can lead to a mix of different OpenTelemetry versions on the classpath, potentially causing runtime errors like NoSuchMethodError.

To ensure version consistency, I recommend using the OpenTelemetry BOM to manage all io.opentelemetry dependencies. You can do this by adding the BOM to a <dependencyManagement> section and removing the explicit <version> tags from individual dependencies.

Example of importing the BOM:

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>io.opentelemetry</groupId>
      <artifactId>opentelemetry-bom</artifactId>
      <version>${opentelemetry.version}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

This will ensure all OpenTelemetry artifacts are on the same version and will simplify future updates.