Update tracing_and_logs

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
opentelemetry (source)	dependencies	minor	0.30.0 -> 0.31.0
opentelemetry-otlp (source)	dependencies	minor	0.30.0 -> 0.31.0
opentelemetry-semantic-conventions (source)	dependencies	minor	0.30.0 -> 0.31.0
opentelemetry_sdk (source)	dependencies	minor	0.30.0 -> 0.31.0
tracing-opentelemetry	dependencies	minor	0.31.0 -> 0.32.0

---

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.31.0

Compare Source

Released 2025-Sep-25

• Breaking Change return type of opentelemetry::global::set_tracer_provider to Unit to align with metrics counterpart
• Add get_all method to opentelemetry::propagation::Extractor to return all values of the given propagation key and provide a default implementation.

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

v0.31.0

Compare Source

Released 2025-Sep-25

• Update opentelemetry-proto and opentelemetry-http dependency version to 0.31.0
• Add HTTP compression support with gzip-http and zstd-http feature flags
• Add retry with exponential backoff and throttling support for HTTP and gRPC exporters

open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)

v0.31.0

Compare Source

Released 2025-Sep-25

• Update to v1.34.0 of the semantic conventions.

open-telemetry/opentelemetry-rust (opentelemetry_sdk)

v0.31.0

Compare Source

Released 2025-Sep-25

• Updated opentelemetry and opentelemetry-http dependencies to version 0.31.0.

• Feature: Add span flags support for isRemote property in OTLP exporter (#​3153)

• Updated span and link transformations to properly set flags field (0x100 for local, 0x300 for remote)

• TODO: Placeholder for Span processor related things

  • Fix SpanProcessor::on_start is no longer called on non recording spans

• Fix: Restore true parallel exports in the async-native BatchSpanProcessor by honoring OTEL_BSP_MAX_CONCURRENT_EXPORTS (#​2959). A regression in #​2685 inadvertently awaited the export() future directly in opentelemetry-sdk/src/trace/span_processor_with_async_runtime.rs instead of spawning it on the runtime, forcing all exports to run sequentially.

• Feature: Added Clone implementation to SdkLogger for API consistency with SdkTracer (#​3058).

• Fix: batch size accounting in BatchSpanProcessor when queue is full (#​3089).

• Fix: Resolved dependency issue where the "logs" feature incorrectly
  required the "trace" feature flag
  (#​3096).
  The logs functionality now operates independently, while automatic correlation
  between logs and traces continues to work when the "trace" feature is
  explicitly enabled.

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

v0.32.0

Compare Source

Added

• Add configuration for including target in spans (#​222)

Changed

• OpenTelemetry context activation (#​202)
  • Trace ID and span ID can be obtained from OtelData via dedicated functions. Note that these
    will be available only if the context has already been built. (#​233)
• Correctly track entered and exited state for timings (#​212)
• Slightly improve error message on version mismatch (#​211)
• Remove Lazy for thread_local static (#​215)
• Update description of special fields and semantic conventions

Breaking Changes

• The attributes code.filepath, code.lineno, and code.namespace have been renamed to
  code.file.path, and code.line.number, and code.module.name, to align with the opentelemetry
  semantic conventions for code. (#​225)
• Upgrade from opentelemetry to 0.31.0. Refer to the upstream
  changelog
  for more information. (#​230)
• Hold onto MetricsProvider in MetricsLayer (#​224)
• The attribute otel.status_message was changed to otel.status_description to align with the
  opentelemetry semantic conventions for code. (#​209)
• Remove the metrics_gauge_unstable feature.

---

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.

👻 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.