This repository was archived by the owner on Apr 15, 2025. It is now read-only.
fix(deps): update opentelemetry-rust monorepo to 0.29.0 #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.21.0->0.29.00.18.0->0.29.00.10.0->0.29.00.14.0->0.29.00.11.0->0.29.00.13.0->0.29.00.10.0->0.29.00.2.0->0.29.00.21.1->0.29.0Release Notes
open-telemetry/opentelemetry-rust (opentelemetry)
v0.29.0Compare Source
Released 2025-Mar-21
ExportErrortrait fromopentelemetry::trace::ExportErrortoopentelemetry_sdk::export::ExportErrorTraceErrorenum fromopentelemetry::trace::TraceErrortoopentelemetry_sdk::trace::TraceErrorTraceResulttype alias fromopentelemetry::trace::TraceResulttoopentelemetry_sdk::trace::TraceResultInstrumentationScopeimplementation forPartialEqandHashfixed to include Attributes also.BaggagefromValuetoStringValueBaggageconstants to reflect latest standard (MAX_KEY_VALUE_PAIRS- 180 -> 64,MAX_BYTES_FOR_ONE_PAIR- removed) and increased insert performance see #2284.Baggage.remove()signature with.get()to take the key as a referenceBaggagecan't be retrieved from theContextdirectly anymore and needs to be accessed viacontext.baggage()with_baggage()andcurrent_with_baggage()override any existingBaggagein theContextBaggagekeys can't be empty and only allow ASCII visual chars, except"(),/:;<=>?@​[\]{}(see RFC7230, Section 3.2.6)KeyValueMetadatadoes not publicly expose its fields. This should be transparent change to the users.Contextto use a stack to properly handle out of order dropping ofContextGuard. This imposes a limit of65535nested contexts on a single thread. See #2378 and #1887.name: Option<&str>parameter to theevent_enabledmethodon the
Loggertrait. This allows implementations (SDK, processor, exporters)to leverage this additional information to determine if an event is enabled.
v0.28.0Compare Source
Released 2025-Feb-10
opentelemetry::global::shutdown_tracer_provider()Removed from this crate, should now usetracer_provider.shutdown()see #2369 for a migration example.opentelemetry::PropagationErrorstruct.v0.27.1Compare Source
Released 2024-Nov-27
v0.27.0Compare Source
Released 2024-Nov-11
LogRecord::set_trace_context; an optional method conditional on thetracefeature for setting trace context on a log record.as_anyfromAsyncInstrumenttrait and the implementing instruments:ObservableCounter,ObservableGauge, andObservableUpDownCounter#2187SyncInstrumenttrait to replace the individual synchronous instrument traits (SyncCounter,SyncGauge,SyncHistogram,SyncUpDownCounter) which are meant for SDK implementation. #2207observemethod on asynchronous instruments can only be called inside a callback. This was done by removing the implementation ofAsyncInstrumenttrait for each of the asynchronous instruments. #2210PartialOrdandOrdimplementations forKeyValue. #2215KeyValuerelated structs and enums asnon_exhaustive. #2228AnyValueenum asnon_exhaustive. #2230initmethod used to create instruments has been renamed tobuild. Also,try_init()method is removed from instrument builders. The return types ofInstrumentProvidertrait methods modified to return the instrument struct, instead ofResult. #2227Before:
Now:
Breaking change: #2220
InstrumentationLibrary::newInstrumentationLibrarytoInstrumentationScopeInstrumentationLibraryBuildertoInstrumentationScopeBuilderLoggerProvider::versioned_loggerandTracerProvider::versioned_tracerLoggerProvider::logger_builder,TracerProvider::tracer_builderandMeterProvider::versioned_meterLoggerProvider::logger_with_scope,TracerProvider::logger_with_scope,MeterProvider::meter_with_scopeglobal::meter_with_versionwithglobal::meter_with_scopeglobal::tracer_with_scopeBreaking change: replaced
InstrumentationScopepublic attributes by getters #2275Breaking change: #2260
global::set_error_handlerandglobal::handle_error.global::handle_errorusage inside the opentelemetry crates has been replaced withglobal::otel_info,otel_warn,otel_debugandotel_errormacros based on the severity of the internal logs.global::handle_errorwas to log the error usingeprintln!. With otel macros, the internal logs get emitted viatracingmacros of matching severity. Users now need to configure atracinglayer/subscriber to capture these logs.tracing::fmtlayer.Breaking change for exporter/processor authors: #2266
ExportErrortrait fromopentelemetry::ExportErrortoopentelemetry_sdk::export::ExportErroropentelemetry::trace::ExportErrorfor trace API. This would be eventually be consolidated with ExportError in the SDK.LogErrorenum fromopentelemetry::logs::LogErrortoopentelemetry_sdk::logs::LogErrorLogResulttype alias fromopentelemetry::logs::LogResulttoopentelemetry_sdk::logs::LogResultMetricErrorenum fromopentelemetry::metrics::MetricErrortoopentelemetry_sdk::metrics::MetricErrorMetricResulttype alias fromopentelemetry::metrics::MetricResulttoopentelemetry_sdk::metrics::MetricResultThese 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 flagtospec_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.0Compare 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 existingKeyValue::new()API covers all the scenarios offered by these APIs.Removed:
ObjectSafeMeterProviderandGlobalMeterProvider#2112. These APIs were unnecessary and were mainly meant for internal use.Modified:
MeterProvider.meter()andMeterProvider.versioned_meter()argument types have been updated to&'static strinstead ofimpl Into<Cow<'static, str>>>#2112. These APIs were modified to enforce the Metername,version, andschema_urlto be&'static str.Renamed:
NoopMeterCoretoNoopMeterAdded
with_boundariesAPI to allow users to provide custom bounds for Histogram instruments. #2135v0.25.0Compare Source
Before:
After:
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_callbackto provide the callback, providethem using
with_callbackmethod, while creating the Observable instrumentitself.
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.0Compare Source
Add "metrics", "logs" to default features. With this, default feature list is
"trace", "metrics" and "logs".
When "metrics" feature is enabled,
KeyValueimplementsPartialEq,Eq,PartialOrder,Order,Hash. This is meant to be used for metricsaggregation purposes only.
Removed
Unitstruct for specifying Instrument units. Unit is treated as anopaque 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.
v0.23.0Compare Source
Added
PropagationErrorGaugeno longer requiresotel-unstablefeature flag, as OpenTelemetry specification forGaugeinstrument is stable.Removed
urlencodingcrate dependency. #1613LoggerProviders are not meant for end users to get loggers from. It is only required for the log bridges.
Below global constructs for the logs are removed from API:
- opentelemetry::global::logger
- opentelemetry::global::set_logger_provider
- opentelemetry::global::shutdown_logger_provider
- opentelemetry::global::logger_provider
- opentelemetry::global::GlobalLoggerProvider
- opentelemetry::global::ObjectSafeLoggerProvider
For creating appenders using Logging bridge API, refer to the opentelemetry-tracing-appender example
Changed
BREAKING Moving LogRecord implementation to the SDK. 1702.
LogRecordstruct to SDK.LogRecordtrait in the API for populating log records. This trait is implemented by the SDK.This is the breaking change for the authors of Log Appenders. Refer to the opentelemetry-appender-tracing for more details.
Deprecate
versioned_logger()in favor oflogger_builder()1567.Before:
After:
versioned_tracer()in favor oftracer_builder()1567.Before:
After:
v0.22.0Compare Source
Added
#1410 Add experimental synchronous gauge. This is behind the feature flag, and can be enabled by enabling the feature
otel_unstablefor opentelemetry crate.#1410 Guidelines to add new unstable/experimental features.
Changed
AnyValue.Mapto be backed byHashMapinstead of customOrderMap,which internally used
IndexMap. There was no requirement to maintain the orderof entries, so moving from
IndexMaptoHashMapoffers slight performancegains, and avoids
IndexMapdependency. This affectsbodyandattributesofLogRecord.#1353
TextMapCompositePropagator#1373NoopLoggerto save on operations#1455
Removed
OrderMaptype as there was no requirement to use this over regularHashMap.#1353
global::shutdown_meter_provider, useSdkMeterProvider::shutdowndirectly instead #1412.
open-telemetry/opentelemetry-rust (opentelemetry-http)
v0.29.0Compare Source
Released 2025-Mar-21
opentelemetrydependency version to 0.29.v0.28.0Compare Source
Released 2025-Feb-10
opentelemetrydependency version to 0.28.tracingcrate.HttpClient::send_byteswithbytes::Bytesrequest payload and deprecate oldHttpClient::sendfunction.v0.27.0Compare Source
Released 2024-Nov-08
Update
opentelemetrydependency version to 0.27Bump MSRV to 1.70 #2179
v0.26.0Compare Source
Released 2024-Sep-30
opentelemetrydependency version to 0.26v0.25.0Compare Source
opentelemetrydependency version to 0.25opentelemetrycrateon major,minor versions.
v0.13.0Compare Source
isahcHTTP client #1924httpv1 #1674opentelemetrydependency version to 0.24v0.12.0Compare Source
reqwest-rustls-webkpi-rootsfeature flag to configurereqwestto use embeddedwebkpi-roots.opentelemetrydependency version to 0.23v0.11.1Compare Source
reqwestusage to use rustls viareqwest/rustls-tlsfeature flag1638.
v0.11.0Compare Source
Changed
ResponseExttrait to returnHttpErrorinstead ofTraceError#1484open-telemetry/opentelemetry-rust (opentelemetry-otlp)
v0.29.0Compare Source
Released 2025-Mar-21
Update
opentelemetrydependency version to 0.29Update
opentelemetry_sdkdependency version to 0.29Update
opentelemetry-httpdependency version to 0.29Update
opentelemetry-protodependency version to 0.29The
OTEL_EXPORTER_OTLP_TIMEOUT,OTEL_EXPORTER_OTLP_TRACES_TIMEOUT,OTEL_EXPORTER_OTLP_METRICS_TIMEOUTandOTEL_EXPORTER_OTLP_LOGS_TIMEOUTare changed from seconds to miliseconds.Fixed
.with_headers()inHttpExporterBuilderto correctly support multiple key/value pairs. #2699Fixed
#2770
partially to properly handle
shutdown()when usinghttp. (tonicstilldoes not do proper shutdown)
Breaking
ExporterBuilder's build() method now Result with
ExporterBuildErrorbeing theError variant. Previously it returned signal specific errors like
LogErrorfrom the
opentelemetry_sdk, which are no longer part of the sdk. No changesrequired if you were using unwrap/expect. If you were matching on the returning
Error enum, replace with the enum
ExporterBuildError. Unlike the previousErrorwhich contained many variants unrelated to building an exporter, thenew one returns specific variants applicable to building an exporter. Some
variants might be applicable only on select features.
Also, now unused
Errorenum is removed.Breaking
ExportConfig'stimeoutfield 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.endpointOTEL_EXPORTER_OTLP_TIMEOUT->ExportConfig.timeoutv0.28.0Compare Source
Released 2025-Feb-10
opentelemetrydependency version to 0.28.opentelemetry_sdkdependency version to 0.28.opentelemetry-httpdependency version to 0.28.opentelemetry-protodependency version to 0.28.LogRecord's
event_name()is now automatically populated on the newly added"event_name" field in LogRecord proto definition.
"reqwest-blocking-client" features as default, to align with the
specification.
2516
opentelemetry_otlp::metrics::MetricsClientand
MetricExporter::new(..)method. UseMetricExporter::builder()...build()to obtainMetricExporter.export timeout interval configured in below order
OTEL_EXPORTER_OTLP_TRACES_TIMEOUT,OTEL_EXPORTER_OTLP_LOGS_TIMEOUTorOTEL_EXPORTER_OTLP_TIMEOUT.OTEL_EXPORTER_OTLP_TIMEOUTenv variable.with_http().with_timeout()API method ofLogExporterBuilderandSpanExporterBuilderandMetricsExporterBuilder.v0.27.0Compare Source
Released 2024-Nov-11
Update
opentelemetrydependency version to 0.27Update
opentelemetry_sdkdependency version to 0.27Update
opentelemetry-httpdependency version to 0.27Update
opentelemetry-protodependency version to 0.27BREAKING:
(#2217) Replaced: The
MetricsExporterBuilderinterface is modified fromwith_temporality_selectortowith_temporalityexample can be seen below:Previous Signature:
Updated Signature:
(#2221) Replaced:
opentelemetry_otlp::new_pipeline().{trace,logging,metrics}()interface is now replaced with{TracerProvider,SdkMeterProvider,LoggerProvider}::builder().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:
Updated Signature:
Renamed
MetricsExporter->MetricExporterMetricsExporterBuilder->MetricExporterBuilder#2263
Support
hyperclient for opentelemetry-otlp. This can be enabled using flaghyper-client.Refer example: https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-otlp/examples/basic-otlp-http
v0.26.0Compare Source
Released 2024-Sep-30
opentelemetrydependency version to 0.26opentelemetry_sdkdependency version to 0.26opentelemetry-httpdependency version to 0.26opentelemetry-protodependency version to 0.26v0.25.0Compare Source
opentelemetrydependency version to 0.25opentelemetry_sdkdependency version to 0.25opentelemetry-httpdependency version to 0.25opentelemetry-protodependency version to 0.25opentelemetrycrateon major,minor versions.
The logrecord event-name is added as an attribute only if the feature flag
populate-logs-event-nameis enabled. The name of the attribute is changed from"name" to "event.name".
1994,
2050
v0.17.0Compare Source
"trace", "metrics" and "logs".
OtlpMetricPipeline.build()no longer invoke theglobal::set_meter_provider. User who setup the pipeline must do itthemselves using
global::set_meter_provider(meter_provider.clone());.with_resourceonOtlpLogPipeline, replacing thewith_configmethod.Instead of using
.with_config(Config::default().with_resource(RESOURCE::default()))users mustnow use
.with_resource(RESOURCE::default())to configure Resource when usingOtlpLogPipeline.OtlpTracePipeline::install_simple()andOtlpTracePipeline::install_batch()would now returnTracerProviderinstead ofTracer.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.previous release.
targetfromLogRecord, if target is populated.LogRecordandSpanby their resource and instrumentation scope before exporting, for better efficiency #1873.httpv1 andtonicv0.12 #1674opentelemetrydependency version to 0.24opentelemetry_sdkdependency version to 0.24opentelemetry-httpdependency version to 0.13opentelemetry-protodependency version to 0.7v0.16.0Compare Source
Fixed
OTEL_EXPORTER_OTLP_HEADERSare now correctly decoded. #1578ExportConfig#1706/v1/traces) #1706OTEL_EXPORTER_OTLP_PROTOCOL_DEFAULT#1746Added
DeltaTemporalitySelector(#1568)webkpi-rootsfeatures toreqwestandtonicbackendsChanged
LoggerProviderinstead ofLogger. Refer to the basic-otlp and basic-otlp-http examples for how to initialize OTLP Log Exporter to use with OpenTelemetryLogBridge and OpenTelemetryTracingBridge respectively.opentelemetrydependency version to 0.23opentelemetry_sdkdependency version to 0.23opentelemetry-httpdependency version to 0.12opentelemetry-protodependency version to 0.6v0.15.0Compare Source
Added
Changed
Fixed
tonic()to the use correct port. #1556Removed
open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)
v0.29.0Compare Source
Released 2025-Mar-21
v0.28.0Compare Source
Released 2025-Feb-10
v0.27.0Compare Source
Released 2024-Nov-11
v0.26.0Compare Source
Released 2024-Sep-30
Changed
the semantic conventions.
semconv_experimentalto enable experimental semantic conventions.This feature is disabled by default.
v0.25.0Compare Source
Changed
opentelemetrycrateon major,minor versions.
#2000
v0.16.0Compare Source
Changed
opentelemetry_semantic_conventions::traceandopentelemetry_semantic_conventions::resourceintoopentelemetry_semantic_conventions::attribute(which now contains all semantic attributes).traceandresourcenow only contain references to attributes which fall under their respective category.Added
opentelemetry_semantic_conventions::metricto store metric semantic conventions.v0.15.0Compare Source
Changed
#1596
#1681
v0.14.0Compare Source
Changed
#1334
open-telemetry/opentelemetry-rust (opentelemetry-stdout)
v0.29.0Compare Source
Released 2025-Mar-21
opentelemetrydependency version to 0.29.opentelemetry_sdkdependency version to 0.29.v0.28.0Compare Source
Released 2025-Feb-10
opentelemetrydependency version to 0.28.opentelemetry_sdkdependency version to 0.28.StartTimeandEndTimeis printed on aggregation (Sum, Gauge, Histogram, ExpoHistogram) with 2 tabs, previously it was on aggregation data point, with 3 tabs, see #2377 and #2411.ordered-float.LogRecord's
event_name()is now automatically displayed.v0.27.0Compare Source
Released 2024-Nov-11
Update
opentelemetrydependency version to 0.27Update
opentelemetry_sdkdependency version to 0.27Bump MSRV to 1.70 #2179
BREAKING
MetricsExporterBuilderinterface is modified fromwith_temporality_selectortowith_temporalityexample can be seen below:Previous Signature:
MetricsExporter->MetricExporterMetricsExporterBuilder->MetricExporterBuilderv0.26.0Compare Source
Released 2024-Sep-30
opentelemetrydependency version to 0.26opentelemetry_sdkdependency version to 0.26v0.25.0Compare Source
opentelemetrydependency version to 0.25opentelemetry_sdkdependency version to 0.25opentelemetrycrateon major,minor versions.
key
nameonly if the feature flagpopulate-logs-event-nameis enabled.v0.5.0Compare Source
opentelemetrydependency version to 0.24opentelemetry_sdkdependency version to 0.24v0.4.0Compare Source
Changed
opentelemetrydependency version to 0.23opentelemetry_sdkdependency version to 0.23v0.3.0Compare Source
Changed
chronofeatures to reduce number of transitive dependencies. #1569open-telemetry/opentelemetry-rust (opentelemetry_sdk)
v0.29.0Compare Source
Released 2025-Mar-21
opentelemetrydependency to 0.29.opentelemetry-httpdependency to 0.29.Runtimetrait has been simplified and refined. See the #2641for the changes.
async-stdsupport forRuntime, asasync-stdcrate is deprecated.MeterProviderBuilder::with_resource,TracerProviderBuilder::with_resource,LoggerProviderBuilder::with_resourceare now additive (#2677).ExportErrortrait fromopentelemetry::trace::ExportErrortoopentelemetry_sdk::export::ExportErrorTraceErrorenum fromopentelemetry::trace::TraceErrortoopentelemetry_sdk::trace::TraceErrorTraceResulttype alias fromopentelemetry::trace::TraceResulttoopentelemetry_sdk::trace::TraceResultforce_flush()inPushMetricExportersynchronousSpanExportertrait method signature:to
This affects anyone who writes custom exporters, as custom implementations of SpanExporter
should now define export as an
async fn:Breaking The SpanExporter::export() method no longer requires a mutable reference to self.
Before:
After:
Custom exporters will need to internally synchronize any mutable state, if applicable.
Bug Fix:
BatchLogProcessornow correctly callsshutdownon the exporterwhen its
shutdownis invoked.Reduced some info level logs to debug
Breaking for custom LogProcessor/Exporter authors: Changed
nameparameter from
&strtoOption<&str>inevent_enabledmethod on theLogProcessorandLogExportertraits.SdkLoggerno longer passes itsscopename but instead passes the incomingnamewhen invokingevent_enabledon processors.Breaking for custom LogExporter authors:
shutdown()method inLogExportertrait no longer requires a mutable ref toself. If the exporterneeds 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 notintended to be public. If you are authoring custom processor/exporters, use
opentelemetry_sdk::error::OTelSdkErrorandopentelemetry_sdk::error::OTelSdkResult.2790
Breaking for custom
LogProcessorauthors: Changedset_resourceto require mutable ref.
fn set_resource(&mut self, _resource: &Resource) {}Breaking: InMemoryExporter's return type change.
TraceResult<Vec<SpanData>>toResult<Vec<SpanData>, InMemoryExporterError>MetricResult<Vec<ResourceMetrics>>toResult<Vec<ResourceMetrics>, InMemoryExporterError>LogResult<Vec<LogDataWithResource>>toResult<Vec<LogDataWithResource>, InMemoryExporterError>v0.28.0Compare 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
opentelemetrydependency to 0.28.Update
opentelemetry-httpdependency 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 entireInstrument 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
nam
Configuration
📅 Schedule: Branch creation - "* 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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.