fix(deps): update opentelemetry-rust monorepo to 0.32.0

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Type	Update	Change
opentelemetry (source)	dependencies	minor	0.23.0 → 0.32.0
opentelemetry-appender-tracing (source)	dependencies	minor	0.4.0 → 0.32.0
opentelemetry-http (source)	dependencies	minor	0.12.0 → 0.32.0
opentelemetry-otlp (source)	dependencies	minor	0.16.0 → 0.32.0
opentelemetry-prometheus (source)	dependencies	minor	0.16.0 → 0.32.0
opentelemetry-semantic-conventions (source)	dependencies	minor	0.15.0 → 0.32.0
opentelemetry-stdout (source)	dependencies	minor	0.4.0 → 0.32.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.32.0

Compare Source

Released 2026-May-08

• Added BoundCounter<T> and BoundHistogram<T> types that cache resolved
  aggregator references for a fixed attribute set. Created via Counter::bind()
  and Histogram::bind(), bound instruments bypass per-call attribute lookup,
  providing significant performance improvements for hot paths where the same
  attributes are used repeatedly. Both types implement Clone so a single bound
  state can be shared across threads or modules without re-binding. Also adds
  the SyncInstrument::bind() trait method and BoundSyncInstrument<T> trait
  for SDK implementors; the trait method has a no-op default so custom
  SyncInstrument impls degrade gracefully without panicking. Gated behind the
  experimental_metrics_bound_instruments feature flag.
• Add reserve method to opentelemetry::propagation::Injector to hint at the number of elements that will be added to avoid multiple resize operations of the underlying data structure. Has an empty default implementation.
• Breaking Removed the following public fields and methods from the SpanBuilder #​3227:
  • trace_id, span_id, end_time, status, sampling_result
  • with_trace_id, with_span_id, with_end_time, with_status, with_sampling_result
• Added #[must_use] attribute to opentelemetry::metrics::AsyncInstrumentBuilder to add compile time warning when .build() is not called on observable instrument builders, preventing silent failures where callbacks are never registered and metrics are never reported.
• Breaking Moved the following SDK sampling types from opentelemetry::trace to opentelemetry_sdk::trace #​3277:
  • SamplingDecision, SamplingResult
  • These types are SDK implementation details and should be imported from opentelemetry_sdk::trace instead.
• "spec_unstable_logs_enabled" feature flag is removed. The capability (and the
  backing specification) is now stable and is enabled by default.
  3278
• Remove the empty "message" field from tracing events emitted via the internal-logs feature
• Fix panic when calling Context::current() from Drop implementations triggered by ContextGuard cleanup (#​3262).

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.
• Add an IntoIterator implementation for opentelemetry::trace::TraceState to allow iterating through its key-value pair collection.

v0.30.0

Compare Source

Released 2025-May-23

#​2821 Context
based suppression capabilities added: Added the ability to prevent recursive
telemetry generation through new context-based suppression mechanisms. This
feature helps prevent feedback loops and excessive telemetry when OpenTelemetry
components perform their own operations.

New methods added to Context:

• is_telemetry_suppressed() - Checks if telemetry is suppressed in this
  context
• with_telemetry_suppressed() - Creates a new context with telemetry
  suppression enabled
• is_current_telemetry_suppressed() - Efficiently checks if the current thread's context
  has telemetry suppressed
• enter_telemetry_suppressed_scope() - Convenience method to enter a scope where telemetry is
  suppressed

These methods allow SDK components, exporters, and processors to temporarily
disable telemetry generation during their internal operations, ensuring more
predictable and efficient observability pipelines.

• re-export tracing for internal-logs feature to remove the need of adding tracing as a dependency

v0.29.1

Compare Source

Release 2025-Apr-01

• Bug Fix: Re-export WithContext at opentelemetry::trace::context::WithContext #​2879 to restore backwards compatibility
  • 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.

v0.27.1

Compare Source

Released 2024-Nov-27

v0.27.0

Compare Source

Released 2024-Nov-11

• Bump MSRV to 1.70 #​2179
• Add LogRecord::set_trace_context; an optional method conditional on the trace feature for setting trace context on a log record.
• Removed unnecessary public methods named as_any from AsyncInstrument trait and the implementing instruments: ObservableCounter, ObservableGauge, and ObservableUpDownCounter #​2187
• Introduced SyncInstrument trait to replace the individual synchronous instrument traits (SyncCounter, SyncGauge, SyncHistogram, SyncUpDownCounter) which are meant for SDK implementation. #​2207
• Ensured that observe method on asynchronous instruments can only be called inside a callback. This was done by removing the implementation of AsyncInstrument trait for each of the asynchronous instruments. #​2210
• Removed PartialOrd and Ord implementations for KeyValue. #​2215
• Breaking change for exporter authors: Marked KeyValue related structs and enums as non_exhaustive. #​2228
• Breaking change for log exporter authors: Marked AnyValue enum as non_exhaustive. #​2230
• Breaking change for Metrics users: The init method used to create instruments has been renamed to build. Also, try_init() method is removed from instrument builders. The return types of InstrumentProvider trait methods modified to return the instrument struct, instead of Result. #​2227

Before:

let counter = meter.u64_counter("my_counter").init();

Now:

let counter = meter.u64_counter("my_counter").build();

• Breaking change: #​2220

  • Removed deprecated method InstrumentationLibrary::new
  • Renamed InstrumentationLibrary to InstrumentationScope
  • Renamed InstrumentationLibraryBuilder to InstrumentationScopeBuilder
  • Removed deprecated methods LoggerProvider::versioned_logger and TracerProvider::versioned_tracer
  • Removed methods LoggerProvider::logger_builder, TracerProvider::tracer_builder and MeterProvider::versioned_meter
  • Replaced these methods with LoggerProvider::logger_with_scope, TracerProvider::logger_with_scope, MeterProvider::meter_with_scope
  • Replaced global::meter_with_version with global::meter_with_scope
  • Added global::tracer_with_scope
  • Refer to PR description for migration guide.

• Breaking change: replaced InstrumentationScope public attributes by getters #​2275

• Breaking change: #​2260

  • Removed global::set_error_handler and global::handle_error.
  • global::handle_error usage inside the opentelemetry crates has been replaced with global::otel_info, otel_warn, otel_debug and otel_error macros based on the severity of the internal logs.
  • The default behavior of global::handle_error was to log the error using eprintln!. With otel macros, the internal logs get emitted via tracing macros of matching severity. Users now need to configure a tracing layer/subscriber to capture these logs.
  • Refer to PR description for migration guide. Also refer to self-diagnostics example to learn how to view internal logs in stdout using tracing::fmt layer.

• Breaking change for exporter/processor authors: #​2266

  • Moved ExportError trait from opentelemetry::ExportError to opentelemetry_sdk::export::ExportError
  • Created new trait opentelemetry::trace::ExportError for trace API. This would be eventually be consolidated with ExportError in the SDK.
  • Moved LogError enum from opentelemetry::logs::LogError to opentelemetry_sdk::logs::LogError
  • Moved LogResult type alias from opentelemetry::logs::LogResult to opentelemetry_sdk::logs::LogResult
  • Moved MetricError enum from opentelemetry::metrics::MetricError to opentelemetry_sdk::metrics::MetricError
  • Moved MetricResult type alias from opentelemetry::metrics::MetricResult to opentelemetry_sdk::metrics::MetricResult
    These changes shouldn't directly affect the users of OpenTelemetry crate, as these constructs are used in SDK and Exporters. If you are an author of an sdk component/plug-in, like an exporter etc. please use these types from sdk. Refer CHANGELOG.md for more details, under same version section.

• Breaking 2291 Rename logs_level_enabled flag to spec_unstable_logs_enabled. Please enable this updated flag if the feature is needed. This flag will be removed once the feature is stabilized in the specifications.

v0.26.0

Compare Source

Released 2024-Sep-30

• BREAKING Public API changes:

  • Removed: Key.bool(), Key.i64(), Key.f64(), Key.string(), Key.array() #​2090. These APIs were redundant as they didn't offer any additional functionality. The existing KeyValue::new() API covers all the scenarios offered by these APIs.

  • Removed: ObjectSafeMeterProvider and GlobalMeterProvider #​2112. These APIs were unnecessary and were mainly meant for internal use.

  • Modified: MeterProvider.meter() and MeterProvider.versioned_meter() argument types have been updated to &'static str instead of impl Into<Cow<'static, str>>> #​2112. These APIs were modified to enforce the Meter name, version, and schema_url to be &'static str.

  • Renamed: NoopMeterCore to NoopMeter

• Added with_boundaries API to allow users to provide custom bounds for Histogram instruments. #​2135

v0.25.0

Compare Source

• BREAKING #​1993 Box complex types in AnyValue enum
  Before:

#[derive(Debug, Clone, PartialEq)]
pub enum AnyValue {
    /// An integer value
    Int(i64),
    /// A double value
    Double(f64),
    /// A string value
    String(StringValue),
    /// A boolean value
    Boolean(bool),
    /// A byte array
    Bytes(Vec<u8>),
    /// An array of `Any` values
    ListAny(Vec<AnyValue>),
    /// A map of string keys to `Any` values, arbitrarily nested.
    Map(HashMap<Key, AnyValue>),
}

After:

#[derive(Debug, Clone, PartialEq)]
pub enum AnyValue {
    /// An integer value
    Int(i64),
    /// A double value
    Double(f64),
    /// A string value
    String(StringValue),
    /// A boolean value
    Boolean(bool),
    /// A byte array
    Bytes(Box<Vec<u8>>),
    /// An array of `Any` values
    ListAny(Box<Vec<AnyValue>>),
    /// A map of string keys to `Any` values, arbitrarily nested.
    Map(Box<HashMap<Key, AnyValue>>),
}

So the custom log appenders should box these types while adding them in message body, or
attribute values. Similarly, the custom exporters should dereference these complex type values
before serializing.

Breaking :
#​2015 Removed
the ability to register callbacks for Observable instruments on Meter directly.
If you were using meter.register_callback to provide the callback, provide
them using with_callback method, while creating the Observable instrument
itself.
1715
shows the exact changes needed to make this migration. If you are starting new,
refer to the
examples
to learn how to provide Observable callbacks.

v0.24.0

Compare Source

• Add "metrics", "logs" to default features. With this, default feature list is
  "trace", "metrics" and "logs".

• When "metrics" feature is enabled, KeyValue implements PartialEq, Eq,
  PartialOrder, Order, Hash. This is meant to be used for metrics
  aggregation purposes only.

• Removed Unit struct for specifying Instrument units. Unit is treated as an
  opaque string. Migration: Replace .with_unit(Unit::new("myunit")) with
  .with_unit("myunit").

• 1869 Introduced the LogRecord::set_target() method in the log bridge API.
  This method allows appenders to set the target/component emitting the logs.

open-telemetry/opentelemetry-rust (opentelemetry-appender-tracing)

v0.32.0

Released 2026-May-08

• Add tracing span attribute enrichment (experimental). When enabled,
  attributes attached to active tracing spans are copied onto each emitted
  log record. "Span" here refers to a tracing::span! from the
  tracing crate (the appender's source), not an OpenTelemetry span.
  #​3482, #​3505

  Gated behind the new experimental_span_attributes cargo feature. As
  with all experimental_* features in this repo, the API may change without
  a major version bump until it is stabilized; once stable, the feature flag
  will be removed.

  Enrichment is disabled by default (no per-span overhead) and must be
  opted into at runtime via a single builder method that accepts a
  [TracingSpanAttributes] value:

  use opentelemetry_appender_tracing::layer::TracingSpanAttributes;
  
  // Copy all tracing-span attributes onto log records:
  let layer = OpenTelemetryTracingBridge::builder(&provider)
      .with_tracing_span_attributes(TracingSpanAttributes::all())
      .build();
  
  // Or copy only an allowlist of attributes:
  let layer = OpenTelemetryTracingBridge::builder(&provider)
      .with_tracing_span_attributes(TracingSpanAttributes::allowlist(["session.id"]))
      .build();

• Remove the experimental_use_tracing_span_context since
  tracing-opentelemetry now supports activating the OpenTelemetry
  context for the current tracing span. This fixes #​3190 — the
  circular dependency introduced by depending on tracing-opentelemetry
  that depends on opentelemetry.

• "spec_unstable_logs_enabled" feature flag is removed. The capability (and the
  backing specification) is now stable and is enabled by default. #​3278

v0.31.1

Released 2025-Oct-1

• Bump tracing-opentelemetry to 0.32

v0.31.0

Released 2025-Sep-25

• Updated opentelemetry dependency to version 0.31.0.

v0.30.1

Released 2025-June-05

• Bump tracing-opentelemetry to 0.31

v0.30.0

Compare Source

Released 2025-May-23

• Updated opentelemetry dependency to version 0.30.0.

v0.29.1

Released 2025-Mar-24

• Bump tracing-opentelemetry to 0.30

v0.29.0

Released 2025-Mar-21

Fixes 1682.
"spec_unstable_logs_enabled" feature now do not suppress logs for other layers.

The special treatment of the "message" field has been extended when recording
string values. With this change, when a log is emitted with a field named
"message" (and string value), its value is directly assigned to the LogRecord’s
body rather than being stored as an attribute named "message". This offers a
slight performance improvement over previous.

For example, the below will now produce LogRecord with the message value
populated as LogRecord's body:

error!(name: "my-event-name", target: "my-system", event_id = 20, user_name = "otel", user_email = "otel@opentelemetry.io", message = "This is an example message");

Previously, Body was only populated when the below style was used.

error!(name: "my-event-name", target: "my-system", event_id = 20, user_name = "otel", user_email = "otel@opentelemetry.io", "This is an example message");

This style, while slightly slower, should still be used when the value is not a
simple string, but require format arguments as in the below example.

error!(name: "my-event-name", target: "my-system", event_id = 20, user_name = "otel", user_email = "otel@opentelemetry.io", "This is an example message with format arguments {} and {}", "foo", "bar");

Fixes 2658
InstrumentationScope(Logger) used by the appender now uses an empty ("") named
Logger. Previously, a Logger with name and version of the crate was used.
Receivers (processors, exporters) are expected to use LogRecord.target() as
scope name. This is already done in OTLP Exporters, so this change should be
transparent to most users.

• Passes event name to the event_enabled method on the Logger. This allows
  implementations (SDK, processor, exporters) to leverage this additional
  information to determine if an event is enabled.

• u64, i128, u128 and usize values are stored as opentelemetry::logs::AnyValue::Int
  when conversion is feasible. Otherwise stored as
  opentelemetry::logs::AnyValue::String. This avoids unnecessary string
  allocation when values can be represented in their original types.

• Byte arrays are stored as opentelemetry::logs::AnyValue::Bytes instead
  of string.

• Error fields are reported using attribute named "exception.message". For
  example, the below will now report an attribute named "exception.message",
  instead of previously reporting the user provided attribute "error".
  error!(....error = &OTelSdkError::AlreadyShutdown as &dyn std::error::Error...)

• perf - small perf improvement by avoiding string allocation of target

• Update opentelemetry dependency version to 0.29.

v0.28.1

Compare Source

Released 2025-Feb-12

• New experimental feature to use trace_id & span_id from spans created through the tracing crate (experimental_use_tracing_span_context) #​2438

v0.28.0

Compare Source

Released 2025-Feb-10

• Update opentelemetry dependency version to 0.28.
• Bump msrv to 1.75.0.

v0.27.0

Compare Source

Released 2024-Nov-11

• Update opentelemetry dependency version to 0.27

• Bump MSRV to 1.70 #​2179

• Breaking 2291 Rename logs_level_enabled flag to spec_unstable_logs_enabled. Please enable this updated flag if the feature is needed. This flag will be removed once the feature is stabilized in the specifications.

v0.26.0

Compare Source

Released 2024-Sep-30

• Update opentelemetry dependency version to 0.26
• 2101 The log events emitted via the tracing pipeline using the log-tracing crate no longer include the target metadata as attributes. Exporters or backends that rely on this attribute should now access the target directly from the LogRecord::target field.

v0.25.0

Compare Source

• Update opentelemetry dependency version to 0.25
• Starting with this version, this crate will align with opentelemetry crate
  on major,minor versions.
• Reduce heap allocation by using &'static str for SeverityText.

v0.5.0

Compare Source

• 1869 Utilize the LogRecord::set_target() method to pass the tracing target to the SDK.
  Exporters might use the target to override the instrumentation scope, which previously contained "opentelemetry-appender-tracing".

• Breaking 1928 Insert tracing event name into LogRecord::event_name instead of attributes.

  • If using a custom exporter, then they must serialize this field directly from LogRecord::event_name instead of iterating over the attributes. OTLP Exporter is modified to handle this.

• Update opentelemetry dependency version to 0.24

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

v0.32.0

Compare Source

Released 2026-May-08

• reqwest's crypto backend has changed from ring to aws-lc-sys.

v0.31.0

Released 2025-Sep-25

• Implementation of Extractor::get_all for HeaderExtractor
• Support HttpClient implementation for HyperClient<C> with custom connectors beyond HttpConnector, enabling Unix Domain Socket connections and other custom transports
• Add reqwest and reqwest-blocking features to enable async and blocking
  reqwest HTTP clients
• Updated opentelemetry dependency to version 0.31.0.

v0.30.0

Compare Source

Released 2025-May-23

• Updated opentelemetry dependency to version 0.30.0.

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.

v0.27.0

Compare Source

Released 2024-Nov-08

• Update opentelemetry dependency version to 0.27

• Bump MSRV to 1.70 #​2179

v0.26.0

Compare Source

Released 2024-Sep-30

• Update opentelemetry dependency version to 0.26

v0.25.0

Compare Source

• Update opentelemetry dependency version to 0.25
• Starting with this version, this crate will align with opentelemetry crate
  on major,minor versions.

v0.13.0

Compare Source

• Breaking Correct the misspelling of "webkpi" to "webpki" in features #​1842
• Breaking Remove support for the isahc HTTP client #​1924
• Update to http v1 #​1674
• Update opentelemetry dependency version to 0.24

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

v0.32.0

Compare Source

Released 2026-May-08

• Add tls-provider-agnostic feature flag for environments that require a custom crypto backend (e.g., OpenSSL for FIPS compliance). Enables TLS code paths without bundling ring or aws-lc-rs.
• Add build() directly on SpanExporterBuilder, MetricExporterBuilder, and LogExporterBuilder
  (before selecting a transport), which auto-selects the transport based on the
  OTEL_EXPORTER_OTLP_PROTOCOL environment variable or enabled features.
  #​3394
• Breaking Removed ExportConfig, HasExportConfig, with_export_config(), HasTonicConfig, HasHttpConfig, TonicConfig, and HttpConfig from public API.
  Use the public WithExportConfig, WithTonicConfig, and WithHttpConfig trait methods instead, which remain unchanged.
• The gRPC/tonic OTLP exporter's build method now returns an error for all signals (traces, metrics, logs) when
  an https:// endpoint is configured but no TLS feature (tls-ring or tls-aws-lc) is enabled, instead of
  silently sending unencrypted traffic. When a TLS feature is enabled and an https:// endpoint is used without
  an explicit .with_tls_config(), a default ClientTlsConfig is automatically applied.
  #​3182
• Prevent auth tokens from leaking in export error messages. gRPC and HTTP
  exporter errors no longer include potentially sensitive server responses
  (e.g., authentication tokens echoed back). Error messages returned to SDK
  processors contain only the gRPC status code or HTTP status code. Full
  details are logged at DEBUG level only.
  #​3021
• Surface pre-flight transport error details at ERROR level when grpc-tonic
  OTLP export fails due to a local misconfiguration. When the returned
  tonic::Status wraps a local transport error (invalid URL, connect failure,
  DNS), its source chain (e.g., "transport error: invalid URI") is appended
  to the returned error so SDK processors surface it at ERROR without
  requiring DEBUG logging. Server-returned gRPC status messages remain
  DEBUG-only to preserve the auth-token leak safeguards from
  #​3021.
  #​3331
• Add support for per-signal protocol environment variables:
  OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, OTEL_EXPORTER_OTLP_METRICS_PROTOCOL,
  OTEL_EXPORTER_OTLP_LOGS_PROTOCOL. These allow configuring different transport protocols
  per signal type. Signal-specific vars take precedence over generic OTEL_EXPORTER_OTLP_PROTOCOL.
  The auto-select build() method on each exporter builder now respects the full priority chain:
  signal-specific env var > generic env var > feature-based default.
• Transport/protocol mismatch validation: HTTP transport returns InvalidConfig when gRPC protocol
  is requested; gRPC transport returns InvalidConfig when an HTTP protocol is requested.
• Breaking: Protocol::default() no longer consults the OTEL_EXPORTER_OTLP_PROTOCOL
  environment variable. It now returns only the feature-based default (http-json > http-proto >
  grpc-tonic). Protocol resolution from environment variables is handled internally by the
  exporter builders. Users who relied on Protocol::default() to read env vars should use
  Protocol::from_env() instead.
• Add support for OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE environment variable
  to configure metrics temporality. Accepted values: cumulative (default), delta,
  lowmemory (case-insensitive). Programmatic .with_temporality() overrides the env var.
• Fix NoHttpClient error when multiple HTTP client features are enabled by using priority-based selection (reqwest-client > hyper-client > reqwest-blocking-client). #​2994
• Add partial success response handling for OTLP exporters (traces, metrics, logs) per OTLP spec. Exporters now log warnings when the server returns partial success responses with rejected items and error messages. #​865
• Refactor internal-logs feature in opentelemetry-otlp to reduce unnecessary dependencies3191
• Fixed [#​2777](https://github.com/open-telemetry/opentelemetry rust/issues/2777) to properly handle shutdown_with_timeout() when using grpc-tonic.
• Deprecate tls feature in favor of explicit tls-ring and tls-aws-lc features.
  Migration: Replace tls with tls-ring (or tls-aws-lc). Users of tls-roots or tls-webpki-roots must now also enable one of these.
• Prevent logging of header values in OTLP tonic exporter #​3465

v0.31.1: opentelemetry-otlp 0.31.1

Compare Source

What's Changed

• feat(OTLP): add tls-ring, tls-aws-lc, and tls-provider-agnostic feature flags [patch release v0.31.1] by @​lalitb in #​3426

Full Changelog: open-telemetry/opentelemetry-rust@v0.31.0...opentelemetry-otlp-0.31.1

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
  This behaviour is opt in via the experimental-grpc-retry and experimental-http-retry flags on this crate. You can customize the retry policy using the with_retry_policy on the exporter builders.

v0.30.0

Compare Source

Released 2025-May-23

• Update opentelemetry dependency version to 0.30
• Update opentelemetry_sdk dependency version to 0.30
• Update opentelemetry-http dependency version to 0.30
• Update opentelemetry-proto dependency version to 0.30
• Update tonic dependency version to 0.13
• Re-export tonic types under tonic_types
  2898
• Publicly re-exported MetricExporterBuilder, SpanExporterBuilder, and
  LogExporterBuilder types, enabling users to directly reference and use these
  builder types for metrics, traces, and logs exporters.
  2966

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

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

v0.27.0

Compare Source

Released 2024-Nov-11

• Update opentelemetry dependency version to 0.27

• Update opentelemetry_sdk dependency version to 0.27

• Update opentelemetry-http dependency version to 0.27

• Update opentelemetry-proto dependency version to 0.27

• BREAKING:

  • (#​2217) Replaced: The MetricsExporterBuilder interface is modified from with_temporality_selector to with_temporality example can be seen below:
    Previous Signature:

    MetricsExporterBuilder::default().with_temporality_selector(DeltaTemporalitySelector::new())

    Updated Signature:

    MetricsExporterBuilder::default().with_temporality(opentelemetry_sdk::metrics::Temporality::Delta)

  • (#​2221) Replaced:

    • The opentelemetry_otlp::new_pipeline().{trace,logging,metrics}() interface is now replaced with {TracerProvider,SdkMeterProvider,LoggerProvider}::builder().
    • The opentelemetry_otlp::new_exporter() interface is now replaced with {SpanExporter,MetricsExporter,LogExporter}::builder().

    Pull request #​2221 has a detailed migration guide in the description. See example below,
    and basic-otlp for more details:

    Previous Signature:

    let logger_provider: LoggerProvider = opentelemetry_otlp::new_pipeline()
      .logging()
      .with_resource(RESOURCE.clone())
      .with_exporter(
          opentelemetry_otlp::new_exporter()
              .tonic()
              .with_endpoint("http://localhost:4317")
      )
      .install_batch(runtime::Tokio)?;

    Updated Signature:

    let exporter = LogExporter::builder()
        .with_tonic()
        .with_endpoint("http://localhost:4317")
        .build()?;
    
    Ok(LoggerProvider::builder()
        .with_resource(RESOURCE.clone())
        .with_batch_exporter(exporter, runtime::Tokio)
        .build())

  • Renamed

    • (#​2255): de-pluralize Metric types.
      • MetricsExporter -> MetricExporter
      • MetricsExporterBuilder -> MetricExporterBuilder

  • #​2263
    Support hyper client for opentelemetry-otlp. This can be enabled using flag hyper-client.
    Refer example: https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-otlp/examples/basic-otlp-http

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

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

v0.32.0

Compare Source

Released 2026-May-08

• Un-deprecate opentelemetry-prometheus and remove stale discontinuation notices. #​3288
• Set MSRV to 1.81.0 to match the prometheus dependency requirement.

[v0.31.0](https://redirect.github.com/open-telemetry/opent

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

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

[github-actions]

Action required: PR inactive for 5 days.
Status update or closure in 10 days.

[github-actions]

Action required: PR inactive for 5 days.
Status update or closure in 10 days.