⬆️ Bump opentelemetry-otlp from 0.29.0 to 0.31.1

[dependabot]

Bumps opentelemetry-otlp from 0.29.0 to 0.31.1.

Release notes

Sourced from opentelemetry-otlp's releases.

opentelemetry-otlp 0.31.1

What's Changed

• feat(OTLP): add tls-ring, tls-aws-lc, and tls-provider-agnostic feature flags [patch release v0.31.1] by @​lalitb in open-telemetry/opentelemetry-rust#3426

Full Changelog: open-telemetry/opentelemetry-rust@v0.31.0...opentelemetry-otlp-0.31.1

Changelog

Sourced from opentelemetry-otlp's changelog.

Release Notes 0.30

OpenTelemetry Rust 0.30 introduces a few breaking changes to the opentelemetry_sdk crate in the metrics feature. These changes were essential to drive the Metrics SDK towards stability. With this release, the Metrics SDK is officially declared stable. The Metrics API was declared stable last year, and previously, the Logs API, SDK, and OTel-Appender-Tracing were also marked stable. Importantly, no breaking changes have been introduced to components already marked as stable.

It is worth noting that the opentelemetry-otlp crate remains in a Release-Candidate state and is not yet considered stable. With the API and SDK for Logs and Metrics now stable, the focus will shift towards further refining and stabilizing the OTLP Exporters in upcoming releases. Additionally, Distributed Tracing is expected to progress towards stability, addressing key interoperability challenges.

For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.

Key Changes

Metrics SDK Improvements

1. Stabilized "view" features: Previously under an experimental feature flag, views can now be used to modify the name, unit, description, and cardinality limit of a metric. Advanced view capabilities, such as changing aggregation or dropping attributes, remain under the experimental feature flag.

2. Cardinality capping: Introduced the ability to cap cardinality and configure limits using views.

3. Polished public API: Refined the public API to hide implementation details from exporters, enabling future internal optimizations and ensuring consistency. Some APIs related to authoring custom metric readers have been moved behind experimental feature flags. These advanced use cases require more time to finalize the API surface before being included in the stable release.

Context-Based Suppression

Added the ability to suppress telemetry based on Context. This feature prevents telemetry-induced-telemetry scenarios and addresses a long-standing issue. Note that suppression relies on proper context propagation. Certain libraries used in OTLP Exporters utilize tracing but do not adopt OpenTelemetry's context propagation. As a result, not all telemetry is automatically suppressed with this feature. Improvements in this area are expected in future releases.

Next Release

... (truncated)

Commits

• febe718 feat(OTLP): add tls-ring, tls-aws-lc, and tls-provider-agnostic feature flags...
• 285dc92 chore: Prepare for release v0.31.0 (#3179)
• 9cde968 chore: Prepare for release otel-http v0.30.1, Revert part of multi-value key ...
• 5250df2 fix: Suppress telemetry emitted inside of BatchLogProcessor::emit (#3172)
• 9bd2c1b fix: use instrumentation schema URL on scope spans (#3171)
• 159135c feat: Add is_remote flag in exporter for spans and span links (#3153)
• b7ff11b fix: Use path+version dependencies for publishing to crates.io otel-http (#3...
• 24da5c9 fix: Use path+version dependencies for publishing to crates.io (#3167)
• 6f75c58 fix: Add std feature to serde to fix CI linting issues (#3165)
• 80b5dcb chore: Bump opentelemetry-proto to v0.30.1 and opentelemetry-otlp to v0.30.1 ...
• Additional commits viewable in compare view

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.