hash Update `opentelemetry` Rust crates

This PR contains the following updates:

Package	Type	Update	Change
opentelemetry	dependencies	minor	`0.23.0` -> `0.24.0`
opentelemetry-otlp (source)	dependencies	minor	`0.16.0` -> `0.17.0`
opentelemetry_sdk	dependencies	minor	`0.23.0` -> `0.24.0`
tracing-opentelemetry	dependencies	minor	`0.24.0` -> `0.25.0`

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

`v0.24.0`

Compare Source

See individual crate changelogs for details.

open-telemetry/opentelemetry-rust (opentelemetry-otlp)

`v0.17.0`

Compare Source

Add "metrics", "logs" to default features. With this, default feature list is "trace", "metrics" and "logs".
OtlpMetricPipeline.build() no longer invoke the global::set_meter_provider. User who setup the pipeline must do it themselves using global::set_meter_provider(meter_provider.clone());.
Add with_resource on OtlpLogPipeline, replacing the with_config method. Instead of using .with_config(Config::default().with_resource(RESOURCE::default())) users must now use .with_resource(RESOURCE::default()) to configure Resource when using OtlpLogPipeline.
Breaking The methods OtlpTracePipeline::install_simple() and OtlpTracePipeline::install_batch() would now return TracerProvider instead of Tracer. These methods would also no longer set the global tracer provider. It would now be the responsibility of users to set it by calling global::set_tracer_provider(tracer_provider.clone());. Refer to the basic-otlp and basic-otlp-http examples on how to initialize OTLP Trace Exporter.
Breaking Correct the misspelling of "webkpi" to "webpki" in features #1842
Bump MSRV to 1.70 #1840
Fixing the OTLP HTTP/JSON exporter. #1882 - The exporter was broken in the previous release.
Breaking 1869 The OTLP logs exporter now overrides the InstrumentationScope::name field with the target from LogRecord, if target is populated.
Groups batch of LogRecord and Span by their resource and instrumentation scope before exporting, for better efficiency #1873.
Breaking Update to http v1 and tonic v0.12 #1674
Update opentelemetry dependency version to 0.24
Update opentelemetry_sdk dependency version to 0.24
Update opentelemetry-http dependency version to 0.13
Update opentelemetry-proto dependency version to 0.7

tokio-rs/tracing-opentelemetry (tracing-opentelemetry)

`v0.25.0`

Compare Source

Breaking Changes

Upgrade to opentelemetry 0.24. Refer to the upstream changelog for more information.

Fixed

Invalidate sample decision on set parent (#153)
chore: fix on_close() comment (#148)

Configuration

📅 Schedule: Branch creation - "before 4am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

May 16 '24 02:05 renovate[bot]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/@local/tracing/Cargo.toml --workspace
error: failed to parse manifest at `/tmp/renovate/repos/github/hashintel/hash/libs/@local/tracing/Cargo.toml`

Caused by:
  the cargo feature `edition2024` requires a nightly version of Cargo, but this is the `stable` channel
  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
  See https://doc.rust-lang.org/cargo/reference/unstable.html#edition-2024 for more information about using this feature.

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path apps/hash-graph/libs/api/Cargo.toml --workspace
error: failed to parse manifest at `/tmp/renovate/repos/github/hashintel/hash/apps/hash-graph/libs/api/Cargo.toml`

Caused by:
  the cargo feature `edition2024` requires a nightly version of Cargo, but this is the `stable` channel
  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
  See https://doc.rust-lang.org/cargo/reference/unstable.html#edition-2024 for more information about using this feature.

May 16 '24 02:05 renovate[bot]

Superseded by https://github.com/hashintel/hash/pull/4700

Jul 12 '24 10:07 vilkinsons

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 17.93%. Comparing base (cbad1f4) to head (6679cd1). Report is 195 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4468   +/-   ##
=======================================
  Coverage   17.93%   17.93%           
=======================================
  Files         486      486           
  Lines       16325    16325           
  Branches     2498     2498           
=======================================
  Hits         2928     2928           
  Misses      13359    13359           
  Partials       38       38

Flag	Coverage Δ
apps.hash-ai-worker-ts	`1.44% <ø> (ø)`
apps.hash-api	`1.19% <ø> (ø)`
local.hash-backend-utils	`9.17% <ø> (ø)`
local.hash-isomorphic-utils	`1.07% <ø> (ø)`
local.hash-subgraph	`25.96% <ø> (ø)`
rust.deer	`?`
rust.error-stack	`?`
rust.sarif	`?`

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Jul 15 '24 17:07 codecov[bot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Aug 08 '24 14:08 renovate[bot]