Skip to content

chore(deps): bump opentelemetry_sdk from 0.28.0 to 0.31.0 in /engine#6

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/engine/opentelemetry_sdk-0.31.0
Closed

chore(deps): bump opentelemetry_sdk from 0.28.0 to 0.31.0 in /engine#6
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/engine/opentelemetry_sdk-0.31.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 13, 2026 •
edited
Loading

Bumps opentelemetry_sdk from 0.28.0 to 0.31.0.

Changelog

Sourced from opentelemetry_sdk'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
  • 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 ...
  • b70771a chore: bump otel-proto to v1.8.0 (#3156)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Apr 13, 2026
@dependabot
chore(deps): bump opentelemetry_sdk from 0.28.0 to 0.31.0 in /engine
83740ff 
Bumps [opentelemetry_sdk](https://github.com/open-telemetry/opentelemetry-rust) from 0.28.0 to 0.31.0.
- [Release notes](https://github.com/open-telemetry/opentelemetry-rust/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.30.md)
- [Commits](open-telemetry/opentelemetry-rust@opentelemetry_sdk-0.28.0...v0.31.0)

---
updated-dependencies:
- dependency-name: opentelemetry_sdk
  dependency-version: 0.31.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot force-pushed the dependabot/cargo/engine/opentelemetry_sdk-0.31.0 branch from 9277f74 to 83740ff Compare April 13, 2026 23:03
hugocorreia90 added a commit that referenced this pull request Apr 13, 2026
@hugocorreia90
chore(deps): bump remaining Dependabot deps
4c5d336 
- opentelemetry_sdk 0.28 → 0.31 (engine)
- opentelemetry-otlp 0.28 → 0.31 (engine)
- criterion 0.5 → 0.7 (engine, dev-dep)
- @types/vscode ^1.110.0 → ^1.115.0 (vscode)
- typescript-eslint ^8.58.0 → ^8.58.2 (vscode)

Resolves conflicting Dependabot PRs #6, #8, #10, #14, #15.
@hugocorreia90 hugocorreia90 mentioned this pull request Apr 13, 2026
Merged
@hugocorreia90
Copy link
Copy Markdown
Contributor

hugocorreia90 commented Apr 13, 2026

Superseded by #16

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Apr 13, 2026

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot Bot deleted the dependabot/cargo/engine/opentelemetry_sdk-0.31.0 branch April 13, 2026 23:08
hugocorreia90 added a commit that referenced this pull request Apr 13, 2026
@hugocorreia90
chore(deps): bump remaining Dependabot deps (#16)
c0a0c0d 
- opentelemetry_sdk 0.28 → 0.31 (engine)
- opentelemetry-otlp 0.28 → 0.31 (engine)
- criterion 0.5 → 0.7 (engine, dev-dep)
- @types/vscode ^1.110.0 → ^1.115.0 (vscode)
- typescript-eslint ^8.58.0 → ^8.58.2 (vscode)

Resolves conflicting Dependabot PRs #6, #8, #10, #14, #15.
hugocorreia90 added a commit that referenced this pull request May 1, 2026
@hugocorreia90
fix(rocky-bigquery): enrich execute_statement_with_stats via jobs.get…
f445e40 
… for totalBytesBilled (#330)

`stats_from_response` already prefers `statistics.query.totalBytesBilled`
over the top-level `totalBytesProcessed` fallback (PR #326), but the
synchronous `jobs.query` and `jobs.getQueryResults` endpoints don't
include the `statistics` block at all — so every sync query was
falling back to processed bytes, which doesn't apply BigQuery's 10 MB
per-query minimum-bill floor.

This PR adds `BigQueryAdapter::fetch_job_statistics`, an async helper
that calls `GET /projects/<p>/jobs/<id>?location=<loc>` for a job ID
returned by `run_query`. The full Job resource includes the
`statistics` block. `execute_statement_with_stats` now enriches the
response with that block before passing it to `stats_from_response`,
so cost reporting reflects what the BigQuery console actually charges
the user.

One extra HTTP roundtrip per query — `jobs.get` is free and returns
in tens of milliseconds for a fresh job. Best-effort: if `jobs.get`
fails for any reason (transient API error, missing job reference),
the path falls back to the existing `totalBytesProcessed` parsing
with a `debug!` log so a future "cost looks low" debugging session
has the failure reason recorded.

Verified end-to-end:
- New `#[ignore]` integration test runs a real query against
  `INFORMATION_SCHEMA.SCHEMATA` and asserts `bytes_scanned >= 10 MiB`
  — proving the floor is applied (constant queries like `SELECT 1`
  are exempt and don't trigger the floor, so they aren't useful as a
  signal here).
- The merge and time-interval live smoke tests both have their
  assertions tightened from `bytes_scanned > 0` to
  `bytes_scanned >= 10 MiB`. Both now report 20–30 MB across their
  multi-statement runs (one floor per `jobs.query` call).

Drops finding #6 in `live/README.md` — the gap is closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@hugocorreia90