fix(deps): update opentelemetry

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
opentelemetry (source)	dependencies	minor	0.27 -> 0.29
opentelemetry-http (source)	dependencies	minor	0.27 -> 0.29
opentelemetry-otlp (source)	dependencies	minor	0.27 -> 0.29
opentelemetry-semantic-conventions (source)	dependencies	minor	0.27 -> 0.29
opentelemetry-zipkin (source)	dependencies	minor	0.27 -> 0.29
opentelemetry_sdk (source)	dependencies	minor	0.27 -> 0.29
tracing-opentelemetry	dependencies	minor	0.28 -> 0.30
tracing-opentelemetry-instrumentation-sdk (source)	dependencies	minor	0.24 -> 0.28

---

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.29.1

Compare Source

Release 2025-Apr-01

• Bug Fix: Re-export WithContext at opentelemetry::trace::context::WithContext #​2879 to restore backwards compatability
  • The new path for WithContext and FutureExt are in opentelemetry::context as they are independent of the trace signal. Users should prefer this path.

v0.29.0

Compare Source

Released 2025-Mar-21

• Breaking Moved ExportError trait from opentelemetry::trace::ExportError to opentelemetry_sdk::export::ExportError
• Breaking Moved TraceError enum from opentelemetry::trace::TraceError to opentelemetry_sdk::trace::TraceError
• Breaking Moved TraceResult type alias from opentelemetry::trace::TraceResult to opentelemetry_sdk::trace::TraceResult
• Bug Fix: InstrumentationScope implementation for PartialEq and Hash fixed to include Attributes also.
• Breaking changes for baggage users: #​2717
  • Changed value type of Baggage from Value to StringValue
  • Updated Baggage constants to reflect latest standard (MAX_KEY_VALUE_PAIRS - 180 -> 64, MAX_BYTES_FOR_ONE_PAIR - removed) and increased insert performance see #2284.
  • Align Baggage.remove() signature with .get() to take the key as a reference
  • Baggage can't be retrieved from the Context directly anymore and needs to be accessed via context.baggage()
  • with_baggage() and current_with_baggage() override any existing Baggage in the Context
  • Baggage keys can't be empty and only allow ASCII visual chars, except "(),/:;<=>?@&#8203;[\]{} (see RFC7230, Section 3.2.6)
  • KeyValueMetadata does not publicly expose its fields. This should be transparent change to the users.
• Changed Context to use a stack to properly handle out of order dropping of ContextGuard. This imposes a limit of 65535 nested contexts on a single thread. See #2378 and #1887.
• Added additional name: Option<&str> parameter to the event_enabled method
  on the Logger trait. This allows implementations (SDK, processor, exporters)
  to leverage this additional information to determine if an event is enabled.

v0.28.0

Compare Source

Released 2025-Feb-10

• Bump msrv to 1.75.0.
• Breaking opentelemetry::global::shutdown_tracer_provider() Removed from this crate, should now use tracer_provider.shutdown() see #​2369 for a migration example.
• Breaking Removed unused opentelemetry::PropagationError struct.

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency version to 0.29.

v0.28.0

Compare Source

Released 2025-Feb-10

• Update opentelemetry dependency version to 0.28.
• Bump msrv to 1.75.0.
• Add "internal-logs" feature flag (enabled by default), and emit internal logs via tracing crate.
• Add HttpClient::send_bytes with bytes::Bytes request payload and deprecate old HttpClient::send function.

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency version to 0.29

• Update opentelemetry_sdk dependency version to 0.29

• Update opentelemetry-http dependency version to 0.29

• Update opentelemetry-proto dependency version to 0.29

• The OTEL_EXPORTER_OTLP_TIMEOUT, OTEL_EXPORTER_OTLP_TRACES_TIMEOUT, OTEL_EXPORTER_OTLP_METRICS_TIMEOUT and OTEL_EXPORTER_OTLP_LOGS_TIMEOUT are changed from seconds to miliseconds.

• Fixed .with_headers() in HttpExporterBuilder to correctly support multiple key/value pairs. #​2699

• Fixed
  #​2770
  partially to properly handle shutdown() when using http. (tonic still
  does not do proper shutdown)

• Breaking
  ExporterBuilder's build() method now Result with ExporterBuildError being the
  Error variant. Previously it returned signal specific errors like LogError
  from the opentelemetry_sdk, which are no longer part of the sdk. No changes
  required if you were using unwrap/expect. If you were matching on the returning
  Error enum, replace with the enum ExporterBuildError. Unlike the previous
  Error which contained many variants unrelated to building an exporter, the
  new one returns specific variants applicable to building an exporter. Some
  variants might be applicable only on select features.
  Also, now unused Error enum is removed.

• Breaking ExportConfig's timeout field is now optional(Option<Duration>)

• Breaking Export configuration done via code is final. ENV variables cannot be used to override the code config.
  Do not use code based config, if there is desire to control the settings via ENV variables.
  List of ENV variables and corresponding setting being affected by this change.

  • OTEL_EXPORTER_OTLP_ENDPOINT -> ExportConfig.endpoint
  • OTEL_EXPORTER_OTLP_TIMEOUT -> ExportConfig.timeout

v0.28.0

Compare Source

Released 2025-Feb-10

• Update opentelemetry dependency version to 0.28.
• Update opentelemetry_sdk dependency version to 0.28.
• Update opentelemetry-http dependency version to 0.28.
• Update opentelemetry-proto dependency version to 0.28.
• Bump msrv to 1.75.0.
• Feature flag "populate-logs-event-name" is removed as no longer relevant.
  LogRecord's event_name() is now automatically populated on the newly added
  "event_name" field in LogRecord proto definition.
• Remove "grpc-tonic" feature from default, and instead add "http-proto" and
  "reqwest-blocking-client" features as default, to align with the
  specification.
  2516
• Remove unnecessarily public trait opentelemetry_otlp::metrics::MetricsClient
  and MetricExporter::new(..) method. Use
  MetricExporter::builder()...build() to obtain MetricExporter.
• The HTTP clients (reqwest, reqwest-blocking, hyper) now support the
  export timeout interval configured in below order
  • Signal specific env variable OTEL_EXPORTER_OTLP_TRACES_TIMEOUT,
    OTEL_EXPORTER_OTLP_LOGS_TIMEOUT or OTEL_EXPORTER_OTLP_TIMEOUT.
  • OTEL_EXPORTER_OTLP_TIMEOUT env variable.
  • with_http().with_timeout() API method of
    LogExporterBuilder and SpanExporterBuilder and MetricsExporterBuilder.
  • The default interval of 10 seconds is used if none is configured.

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update to v1.31.0 of the semantic conventions.

v0.28.0

Compare Source

Released 2025-Feb-10

• Update to v1.29.0 of the semantic conventions.
• Bump msrv to 1.75.0.

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency version to 0.29.

• Update opentelemetry_sdk dependency version to 0.29.

• Update opentelemetry-http dependency version to 0.29.

• Breaking The ZipkinExporterBuilder::build() method now returns a
  Result<ZipkinExporter, ExporterBuildError>. The ExporterBuildError enum
  lists possible failures specific to the Zipkin exporter and was renamed from
  opentelemetry_zipkin::Error. Previously, this method returned a TraceError
  from the opentelemetry_sdk crate, which was unrelated to Zipkin builder
  failures.
  2839

v0.28.0

Compare Source

Released 2025-Feb-10

• Update opentelemetry dependency version to 0.28.

• Update opentelemetry_sdk dependency version to 0.28.

• Update opentelemetry-http dependency version to 0.28.

• Bump msrv to 1.75.0.

• Breaking The opentelemetry_zipkin::new_pipeline() interface is now replaced with opentelemetry_zipkin::ZipkinExporter::builder().
  Additionally, the service name needs to be set on the tracer provider.

  Previous Signature:

  let tracer = opentelemetry_zipkin::new_pipeline()
      .with_service_name("trace-demo")
      .install_simple()?;

  Updated Signature:

  let exporter = ZipkinExporter::builder()
      .build()?;
  let provider = SdkTracerProvider::builder()
      .with_simple_exporter(exporter)
      .with_service_name("trace-demo")
      .build();
  global::set_tracer_provider(provider.clone());
  
  let tracer = global::tracer("zipkin-tracer");

open-telemetry/opentelemetry-rust (opentelemetry_sdk)

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency to 0.29.
• Update opentelemetry-http dependency to 0.29.
• Breaking: The Runtime trait has been simplified and refined. See the #​2641
  for the changes.
• Removed async-std support for Runtime, as async-std crate is deprecated.
• Calls to MeterProviderBuilder::with_resource, TracerProviderBuilder::with_resource,
  LoggerProviderBuilder::with_resource are now additive (#​2677).
• Moved ExportError trait from opentelemetry::trace::ExportError to opentelemetry_sdk::export::ExportError
• Moved TraceError enum from opentelemetry::trace::TraceError to opentelemetry_sdk::trace::TraceError
• Moved TraceResult type alias from opentelemetry::trace::TraceResult to opentelemetry_sdk::trace::TraceResult
• Breaking: Make force_flush() in PushMetricExporter synchronous
• Breaking: Updated the SpanExporter trait method signature:

  fn export(&mut self, batch: Vec<SpanData>) -> BoxFuture<'static, OTelSdkResult>;

to

  fn export(
    &mut self,
    batch: Vec<SpanData>,
) -> impl std::future::Future<Output = OTelSdkResult> + Send;

This affects anyone who writes custom exporters, as custom implementations of SpanExporter
should now define export as an async fn:

  impl trace::SpanExporter for CustomExporter {
    async fn export(&mut self, batch: Vec<trace::SpanData>) -> OTelSdkResult {
        // Implementation here
    }
}

• Breaking The SpanExporter::export() method no longer requires a mutable reference to self.
  Before:

    async fn export(&mut self, batch: Vec<SpanData>) -> OTelSdkResult

  After:

    async fn export(&self, batch: Vec<SpanData>) -> OTelSdkResult

  Custom exporters will need to internally synchronize any mutable state, if applicable.

• Breaking The shutdown_with_timeout method is added to MetricExporter trait. This is breaking change for custom MetricExporter authors.

• Bug Fix: BatchLogProcessor now correctly calls shutdown on the exporter
  when its shutdown is invoked.

• Reduced some info level logs to debug

• Breaking for custom LogProcessor/Exporter authors: Changed name
  parameter from &str to Option<&str> in event_enabled method on the
  LogProcessor and LogExporter traits. SdkLogger no longer passes its
  scope name but instead passes the incoming name when invoking
  event_enabled on processors.

• Breaking for custom LogExporter authors: shutdown() method in
  LogExporter trait no longer requires a mutable ref to self. If the exporter
  needs to mutate state, it should rely on interior mutability.
  2764

• Breaking (Affects custom Exporter/Processor authors only) Removed
  opentelelemetry_sdk::logs::error::{LogError, LogResult}. These were not
  intended to be public. If you are authoring custom processor/exporters, use
  opentelemetry_sdk::error::OTelSdkError and
  opentelemetry_sdk::error::OTelSdkResult.
  2790

• Breaking for custom LogProcessor authors: Changed set_resource
  to require mutable ref.
  fn set_resource(&mut self, _resource: &Resource) {}

• Breaking: InMemoryExporter's return type change.

  • TraceResult<Vec<SpanData>> to Result<Vec<SpanData>, InMemoryExporterError>
  • MetricResult<Vec<ResourceMetrics>> to Result<Vec<ResourceMetrics>, InMemoryExporterError>
  • LogResult<Vec<LogDataWithResource>> to Result<Vec<LogDataWithResource>, InMemoryExporterError>

v0.28.0

Compare Source

Released 2025-Feb-10

Note: Due to the large amount of making changes, check migration guide to
0.28 for a summary that can help majority users to
quickly migrate. The changelog below is the full list of changes.

• Update opentelemetry dependency to 0.28.

• Update opentelemetry-http dependency to 0.28.

• Bump msrv to 1.75.0.

• Bug fix: For cumulative temporality, ObservableGauge no longer export
  MetricPoints unless measurements were newly reported (in Observable callbacks)
  since last export. This bug fixes ensures ObservableGauge behaves as per OTel
  Spec. The bug is not addressed for other Observable instruments
  #​2213

• Upgrade the tracing crate used for internal logging to version 0.1.40 or
  later. This is necessary because the internal logging macros utilize the name
  field as metadata, a feature introduced in version 0.1.40.
  #​2418

• Feature: Introduced a new feature flag,
  experimental_metrics_disable_name_validation, which disables entire
  Instrument Name Validation. This is an experimental feature to unblock use
  cases requiring currently disallowed characters (eg: Windows Perf Counters).
  Use caution when enabling this feature as this breaks guarantees about metric
  name.

• Bug fix: Empty Tracer names are retained as-is instead of replacing with
  "rust.opentelemetry.io/sdk/tracer"
  #​2486

• Update EnvResourceDetector to allow resource attribute values containing
  equal signs ("=").
  #​2120

• ResourceDetector.detect() no longer supports timeout option.

• Breaking Resource.get() modified to require reference to Key instead of
  owned. Replace get(Key::from_static_str("key")) with
  get(&Key::from_static_str("key"))

• Feature: Add ResourceBuilder for an easy way to create new Resources

• Breaking: Remove

• Resource::{new,empty,from_detectors,new_with_defaults,from_schema_url,merge,default}.
  To create Resources you should only use Resource::builder() or Resource::builder_empty(). See
  #​2322 for a migration guide.

  Example Usage:

  // old
  Resource::default().with_attributes([
      KeyValue::new("service.name", "test_service"),
      KeyValue::new("key", "value"),
  ]);
  
  // new
  Resource::builder()
      .with_service_name("test_service")
      .with_attribute(KeyValue::new("key", "value"))
      .build();

• Breaking :
  #​2314

  • The LogRecord struct has been updated:
    • All fields are now pub(crate) instead of pub.
    • Getter methods have been introduced to access field values. This change
      impacts custom exporter and processor developers by requiring updates to
      code that directly accessed LogRecord fields. They must now use the provided
      getter methods (e.g., log_record.event_name() instead of
      log_record.event_name).

• Breaking (Affects custom metric exporter authors only) start_time and
  time is moved from DataPoints to aggregations (Sum, Gauge, Histogram,
  ExpoHistogram) see
  #​2377 and
  #​2411, to
  reduce memory.

• Breaking start_time is no longer optional for Sum aggregation, see
  #​2367, but
  is still optional for Gauge aggregation see
  #​2389.

• SimpleLogProcessor modified to be generic over LogExporter to avoid
  dynamic dispatch to invoke exporter. If you were using
  with_simple_exporter to add LogExporter with SimpleLogProcessor, this is
  a transparent change.
  #​2338

• Breaking opentelemetry::global::shutdown_tracer_provider() removed from the API,
  should now use tracer_provider.shutdown() see
  #​2369 for
  a migration example. "Tracer provider" is cheaply clonable, so users are
  encouraged to set a clone of it as the global (ex:
  global::set_tracer_provider(provider.clone())), so that instrumentations
  and other components can obtain tracers from global::tracer(). The
  tracer_provider must be kept around to call shutdown on it at the end of
  application (ex: tracer_provider.shutdown())

• Breaking The LogExporter::export() method no longer requires a mutable
  reference to self.: Before: async fn export(&mut self, _batch: LogBatch<'_>) -> LogResult<()> After: async fn export(&self, _batch: LogBatch<'_>) -> LogResult<()> Custom exporters will need to internally synchronize any
  mutable state, if applicable.

• Breaking Removed the following deprecated struct:

  • logs::LogData - Previously deprecated in version 0.27.1 Migration Guidance:
    This structure is no longer utilized within the SDK, and users should not have
    dependencies on it.

• Breaking Removed the following deprecated methods:

  • Logger::provider() : Previously deprecated in version 0.27.1
  • Logger::instrumentation_scope() : Previously deprecated in version 0.27.1.
    Migration Guidance: - These methods were intended for log appender authors.
    Keep the clone of the provider handle, instead of depending on above
    methods.

• Rename opentelemetry_sdk::logs::Builder to
  opentelemetry_sdk::logs::LoggerProviderBuilder.

• Rename opentelemetry_sdk::trace::Builder to
  opentelemetry_sdk::trace::SdkTracerProviderBuilder.

• Redesigned PeriodicReader, BatchSpanProcessor, BatchLogProcessor to no longer
  require an async runtime. They create its own background thread instead. When
  pairing with OTLP, grpc-tonic or reqwest-blocking-client are the only
  supported features (hyper, reqwest are not supported) These are now
  enabled by default and can be migrated to by removing the extra rt:Runtime
  argument as shown below.

  • PeriodicReader::builder(exporter,runtime::Tokio).build(); to
    PeriodicReader::builder(exporter).build();
  • .with_batch_exporter(exporter, runtime::Tokio) to
    .with_batch_exporter(exporter)

  The new implementation has following limitations:

  • Does not work if your application cannot spawn new Thread.
  • Does not support hyper, reqwest HTTP Clients
  • Does not support multiple concurrent exports (with_max_concurrent_exports
    is not supported). This existed only for traces.

  If this applies to you, you can get the old behavior back by following steps
  below:

  • Enable one or more of the feature flag from below
    experimental_metrics_periodicreader_with_async_runtime
experimental_logs_batch_log_processor_with_async_runtime
experimental_trace_batch_span_processor_with_async_runtime
  • Use updated namespace; i.e
    periodic_reader_with_async_runtime::PeriodicReader,
    log_processor_with_async_runtime::BatchLogProcessor and
    span_processor_with_async_runtime::BatchSpanProcessor
  • Continue using existing features flags rt-tokio,
    rt-tokio-current-thread, or rt-async-std.

  As part of the above redesign of PeriodicReader and BatchProcessors, these
  components no longer enforce timeout themselves and instead relies on
  Exporters to enforce own timeouts. In other words, the following are no longer
  supported.

  • with_max_export_timeout, with_timeout methods on BatchConfigBuilder,
    PeriodicReaderBuilder
  • OTEL_BLRP_EXPORT_TIMEOUT, OTEL_BSP_EXPORT_TIMEOUT

  Users are advised to configure timeout on the Exporters itself. For example,
  in the OTLP exporter, the export timeout can be configured using:

  • Environment variables
    • OTEL_EXPORTER_OTLP_TIMEOUT
    • OTEL_EXPORTER_OTLP_LOGS_TIMEOUT, OTEL_EXPORTER_OTLP_TRACES_TIMEOUT,
      OTEL_EXPORTER_OTLP_METRICS_TIMEOUT
  • The opentelemetry_otlp API, via .with_tonic().with_timeout() or
    .with_http().with_timeout().

• Breaking Introduced experimental_async_runtime feature for
  runtime-specific traits.

  • Runtime-specific features (rt-tokio, rt-tokio-current-thread, and
    rt-async-std) now depend on the experimental_async_runtime feature.
  • For most users, no action is required. Enabling runtime features such as
    rt-tokio, rt-tokio-current-thread, or rt-async-std will automatically
    enable the experimental_async_runtime feature.
  • If you're implementing a custom runtime, you must explicitly enable the
    experimental_async_runtimefeature in your Cargo.toml and implement the requiredRuntime` traits.

• Removed Metrics Cardinality Limit feature. This was originally introduced in
  #​1066 with a
  hardcoded limit of 2000 and no ability to change it. This feature will be
  re-introduced in a future date, along with the ability to change the cardinality
  limit.

• Breaking Removed unused opentelemetry_sdk::Error enum.

• Breaking (Affects custom Exporter authors only) Moved ExportError trait
  from opentelemetry::export::ExportError to opentelemetry_sdk::ExportError

• Breaking (Affects custom SpanExporter, SpanProcessor authors only): Rename
  namespaces for Span exporter structs/traits before:
  opentelemetry_sdk::export::spans::{ExportResult, SpanData, SpanExporter};
  now: opentelemetry_sdk::trace::{ExportResult, SpanData, SpanExporter};

• Breaking (Affects custom LogExporter, LogProcessor authors only): Rename
  namespaces for Log exporter structs/traits. before:
  opentelemetry_sdk::export::logs::{ExportResult, LogBatch, LogExporter}; now:
  opentelemetry_sdk::logs::{ExportResult, LogBatch, LogExporter};

• Breaking opentelemetry_sdk::LogRecord::default() method is removed. The
  only way to create log record outside opentelemetry_sdk crate is using
  Logger::create_log_record() method.

• Breaking: Rename namespaces for InMemoryExporters. (The module is still
  under "testing" feature flag)
  before:

  opentelemetry_sdk::testing::logs::{InMemoryLogExporter,
  InMemoryLogExporterBuilder};
  opentelemetry_sdk::testing::trace::{InMemorySpanExporter,
  InMemorySpanExporterBuilder};
  opentelemetry_sdk::testing::metrics::{InMemoryMetricExporter,
  InMemoryMetricExporterBuilder};

  now:

  opentelemetry_sdk::logs::{InMemoryLogExporter, InMemoryLogExporterBuilder};
  opentelemetry_sdk::trace::{InMemorySpanExporter,
  InMemorySpanExporterBuilder};
  opentelemetry_sdk::metrics::{InMemoryMetricExporter,
  InMemoryMetricExporterBuilder};

• Breaking Renamed LoggerProvider, Logger and LogRecord to
  SdkLoggerProvider,SdkLogger and SdkLogRecord respectively to avoid name
  collision with public API types.
  #​2612

• Breaking Renamed TracerProvider and Tracer to SdkTracerProvider and
  SdkTracer to avoid name collision with public API types. Tracer is still
  type-aliased to SdkTracer to keep back-compat with tracing-opentelemetry.
  #​2614

• Breaking Providers, Exporters, Processors, and Readers are modified to use a
  unified Result type for export(), force_flush(), and shutdown() methods.
  All these methods now use OTelSdkResult as their return type. Following PRs
  show the exact changes:
  2613
  2625
  2604
  2606
  2573

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

v0.30.0

Compare Source

Breaking Changes

• Upgrade from opentelemetry 0.28.0 to 0.29.0. Refer to the upstream
  changelog
  for more information.

v0.29.0

Compare Source

What's Changed

• Fix the example installing OpenTelemetryLayer into a global subscriber by @​mzabaluev in https://github.com/tokio-rs/tracing-opentelemetry/pull/175
• Update dependencies by @​djc in https://github.com/tokio-rs/tracing-opentelemetry/pull/187
• Use renamed WASI target by @​djc in https://github.com/tokio-rs/tracing-opentelemetry/pull/189
• use the tracing event name as the otel event name by @​zzlk in https://github.com/tokio-rs/tracing-opentelemetry/pull/188
• Update opentelemetry to 0.28 by @​cschramm in https://github.com/tokio-rs/tracing-opentelemetry/pull/193

davidB/tracing-opentelemetry-instrumentation-sdk (tracing-opentelemetry-instrumentation-sdk)

v0.28.0

Compare Source

Changed

• ⬆️ upgrade to tonic 0.12
• ⬆️ upgrade to rstest 0.22

v0.26.0

Compare Source

Changed

• ⬆️ upgrade to tonic 0.12
• ⬆️ upgrade to rstest 0.22

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), 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.

[Travispersson]

https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/migration_0.28.md