Update opentelemetry Rust crates

[hash-worker]

This PR contains the following updates:

Package	Type	Update	Change
opentelemetry	workspace.dependencies	minor	=0.23.0 -> =0.26.0
opentelemetry-otlp (source)	workspace.dependencies	minor	=0.16.0 -> =0.26.0
opentelemetry_sdk	workspace.dependencies	minor	=0.23.0 -> =0.26.0
tracing-opentelemetry	workspace.dependencies	minor	=0.24.0 -> =0.27.0

---

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.26.0: 0.26.0 Release

Compare Source

See changelog for individual crates to know the exact set of changes. As informed during previous release, all crates from this repo follows same version (0.26.0 for this release).
This release also upgrades Metric API (part of opentelemetry crate) from alpha to beta.

v0.25.0: OpenTelemetry 0.25.0 Release

Compare Source

See changelog for individual crates to know the exact set of changes. This release onwards, all crates from this repo follows same version (0.25.0 for today's release).

v0.24.0

Compare Source

See individual crate changelogs for details.

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

v0.26.0

Compare Source

Released 2024-Sep-30

• Update opentelemetry dependency version to 0.26
• Update opentelemetry_sdk dependency version to 0.26
• Update opentelemetry-http dependency version to 0.26
• Update opentelemetry-proto dependency version to 0.26
• Bump MSRV to 1.71.1 2140

v0.25.0

Compare Source

• Update opentelemetry dependency version to 0.25
• Update opentelemetry_sdk dependency version to 0.25
• Update opentelemetry-http dependency version to 0.25
• Update opentelemetry-proto dependency version to 0.25
• Starting with this version, this crate will align with opentelemetry crate
  on major,minor versions.
• Breaking
  The logrecord event-name is added as an attribute only if the feature flag
  populate-logs-event-name is enabled. The name of the attribute is changed from
  "name" to "event.name".
  1994,
  2050

v0.17.0

Compare Source

• Add "metrics", "logs" to default features. With this, default feature list is
  "trace", "metrics" and "logs".
• Breaking 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.27.0

Compare Source

Breaking Changes

• Upgrade to opentelemetry 0.26. Refer to the upstream
  changelog
  for more information.

v0.26.0

Compare Source

Breaking Changes

• Upgrade to opentelemetry 0.25. Refer to the upstream
  changelog
  for more information.

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 has been generated by Renovate Bot.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 20.23%. Comparing base (5cdb029) to head (2159983).
Report is 118 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5040   +/-   ##
=======================================
  Coverage   20.23%   20.23%           
=======================================
  Files         508      508           
  Lines       17260    17260           
  Branches     2537     2537           
=======================================
  Hits         3492     3492           
  Misses      13730    13730           
  Partials       38       38           

Flag	Coverage Δ
apps.hash-ai-worker-ts	1.39% <ø> (ø)
apps.hash-api	1.19% <ø> (ø)

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hash-worker]

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.

[github-actions]

Benchmark results

@rust/graph-benches – Integrations

representative_read_entity

Function	Value	Mean	Flame graphs
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/book/v/1	$$16.6 \mathrm{ms} \pm 182 \mathrm{μs}\left({\color{lightgreen}-30.614 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/block/v/1	$$16.6 \mathrm{ms} \pm 224 \mathrm{μs}\left({\color{gray}-0.669 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/page/v/2	$$16.3 \mathrm{ms} \pm 183 \mathrm{μs}\left({\color{lightgreen}-28.849 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/playlist/v/1	$$17.8 \mathrm{ms} \pm 187 \mathrm{μs}\left({\color{red}34.4 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/song/v/1	$$16.7 \mathrm{ms} \pm 190 \mathrm{μs}\left({\color{gray}0.352 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/person/v/1	$$16.6 \mathrm{ms} \pm 187 \mathrm{μs}\left({\color{red}6.03 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/uk-address/v/1	$$16.3 \mathrm{ms} \pm 195 \mathrm{μs}\left({\color{gray}-0.139 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/building/v/1	$$15.9 \mathrm{ms} \pm 172 \mathrm{μs}\left({\color{gray}-2.029 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: https://blockprotocol.org/@alice/types/entity-type/organization/v/1	$$15.9 \mathrm{ms} \pm 210 \mathrm{μs}\left({\color{gray}-4.355 \mathrm{\%}}\right) $$	Flame Graph

representative_read_entity_type

Function	Value	Mean	Flame graphs
get_entity_type_by_id	Account ID: d4e16033-c281-4cde-aa35-9085bf2e7579	$$1.41 \mathrm{ms} \pm 3.34 \mathrm{μs}\left({\color{gray}-1.321 \mathrm{\%}}\right) $$	Flame Graph

scaling_read_entity_complete_zero_depth

Function	Value	Mean	Flame graphs
entity_by_id	50 entities	$$4.00 \mathrm{ms} \pm 18.5 \mathrm{μs}\left({\color{gray}3.85 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10 entities	$$2.03 \mathrm{ms} \pm 7.89 \mathrm{μs}\left({\color{gray}-2.782 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	25 entities	$$2.51 \mathrm{ms} \pm 16.6 \mathrm{μs}\left({\color{lightgreen}-9.700 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1 entities	$$1.85 \mathrm{ms} \pm 9.58 \mathrm{μs}\left({\color{gray}-1.239 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	5 entities	$$2.00 \mathrm{ms} \pm 91.5 \mathrm{μs}\left({\color{red}5.15 \mathrm{\%}}\right) $$	Flame Graph

scaling_read_entity_linkless

Function	Value	Mean	Flame graphs
entity_by_id	1000 entities	$$2.78 \mathrm{ms} \pm 23.4 \mathrm{μs}\left({\color{lightgreen}-20.022 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	100 entities	$$2.04 \mathrm{ms} \pm 11.2 \mathrm{μs}\left({\color{gray}-0.263 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10 entities	$$1.88 \mathrm{ms} \pm 6.44 \mathrm{μs}\left({\color{gray}0.778 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10000 entities	$$12.9 \mathrm{ms} \pm 135 \mathrm{μs}\left({\color{red}42.0 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1 entities	$$1.90 \mathrm{ms} \pm 9.61 \mathrm{μs}\left({\color{gray}0.683 \mathrm{\%}}\right) $$	Flame Graph

representative_read_multiple_entities

Function	Value	Mean	Flame graphs
entity_by_property	depths: DT=2, PT=2, ET=2, E=2	$$58.8 \mathrm{ms} \pm 339 \mathrm{μs}\left({\color{gray}0.009 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=255, PT=255, ET=255, E=255	$$69.0 \mathrm{ms} \pm 611 \mathrm{μs}\left({\color{gray}2.05 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=0, PT=0, ET=0, E=0	$$39.7 \mathrm{ms} \pm 362 \mathrm{μs}\left({\color{gray}0.687 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=0, PT=0, ET=0, E=2	$$43.3 \mathrm{ms} \pm 334 \mathrm{μs}\left({\color{gray}-0.092 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=0, PT=2, ET=2, E=2	$$54.8 \mathrm{ms} \pm 370 \mathrm{μs}\left({\color{gray}0.737 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=0, PT=0, ET=2, E=2	$$50.1 \mathrm{ms} \pm 338 \mathrm{μs}\left({\color{gray}-1.110 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=2, PT=2, ET=2, E=2	$$100 \mathrm{ms} \pm 828 \mathrm{μs}\left({\color{gray}0.225 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=255, PT=255, ET=255, E=255	$$110 \mathrm{ms} \pm 1.10 \mathrm{ms}\left({\color{gray}0.455 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=0, PT=0, ET=0, E=0	$$42.2 \mathrm{ms} \pm 478 \mathrm{μs}\left({\color{gray}1.000 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=0, PT=0, ET=0, E=2	$$80.2 \mathrm{ms} \pm 501 \mathrm{μs}\left({\color{gray}-0.416 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=0, PT=2, ET=2, E=2	$$93.8 \mathrm{ms} \pm 297 \mathrm{μs}\left({\color{gray}-0.106 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=0, PT=0, ET=2, E=2	$$89.3 \mathrm{ms} \pm 390 \mathrm{μs}\left({\color{gray}-2.119 \mathrm{\%}}\right) $$	Flame Graph

scaling_read_entity_complete_one_depth

Function	Value	Mean	Flame graphs
entity_by_id	50 entities	$$270 \mathrm{ms} \pm 1.12 \mathrm{ms}\left({\color{lightgreen}-82.173 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10 entities	$$52.9 \mathrm{ms} \pm 286 \mathrm{μs}\left({\color{gray}1.42 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	25 entities	$$73.5 \mathrm{ms} \pm 726 \mathrm{μs}\left({\color{gray}-1.301 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1 entities	$$20.1 \mathrm{ms} \pm 93.1 \mathrm{μs}\left({\color{gray}-0.443 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	5 entities	$$25.1 \mathrm{ms} \pm 66.7 \mathrm{μs}\left({\color{gray}-0.526 \mathrm{\%}}\right) $$	Flame Graph