chore(deps): update opentelemetry to 0.30 #240
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.29
->0.30
0.29
->0.30
0.29
->0.30
0.29
->0.30
0.29
->0.30
0.29
->0.30
0.29
->0.30
0.29
->0.30
Release Notes
open-telemetry/opentelemetry-rust (opentelemetry)
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 thiscontext
with_telemetry_suppressed()
- Creates a new context with telemetrysuppression enabled
is_current_telemetry_suppressed()
- Efficiently checks if the current thread's contexthas telemetry suppressed
enter_telemetry_suppressed_scope()
- Convenience method to enter a scope where telemetry issuppressed
These methods allow SDK components, exporters, and processors to temporarily
disable telemetry generation during their internal operations, ensuring more
predictable and efficient observability pipelines.
tracing
forinternal-logs
feature to remove the need of addingtracing
as a dependencyopen-telemetry/opentelemetry-rust (opentelemetry-jaeger-propagator)
v0.30.0
Compare Source
Released 2025-May-23
opentelemetry
dependency to version 0.30.0.open-telemetry/opentelemetry-rust (opentelemetry-otlp)
v0.30.0
Compare Source
Released 2025-May-23
opentelemetry
dependency version to 0.30opentelemetry_sdk
dependency version to 0.30opentelemetry-http
dependency version to 0.30opentelemetry-proto
dependency version to 0.30tonic
dependency version to 0.13tonic
types undertonic_types
2898
MetricExporterBuilder
,SpanExporterBuilder
, andLogExporterBuilder
types, enabling users to directly reference and use thesebuilder types for metrics, traces, and logs exporters.
2966
open-telemetry/opentelemetry-rust (opentelemetry-proto)
v0.30.0
Compare Source
Released 2025-May-23
opentelemetry
dependency version to 0.30opentelemetry_sdk
dependency to version 0.30.0.tonic
dependency version to 0.13open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)
v0.30.0
Compare Source
Released 2025-May-23
open-telemetry/opentelemetry-rust (opentelemetry-stdout)
v0.30.0
Compare Source
Released 2025-May-23
opentelemetry
dependency to version 0.30.0.opentelemetry_sdk
dependency to version 0.30.0.open-telemetry/opentelemetry-rust (opentelemetry-zipkin)
v0.30.0
Compare Source
Released 2025-May-23
opentelemetry
dependency to version 0.30.0.opentelemetry_sdk
dependency to version 0.30.0.opentelemetry-http
dependency to version 0.30.0.open-telemetry/opentelemetry-rust (opentelemetry_sdk)
v0.30.0
Compare Source
Released 2025-May-23
Updated
opentelemetry
andopentelemetry-http
dependencies to version 0.30.0.It is now possible to add links to a
Span
via theSpanRef
that you get froma
Context
. 2959Feature: Added context based telemetry suppression. #2868
SdkLogger
,SdkTracer
modified to respect telemetry suppression based onContext
. In other words, if the current context has telemetry suppressionenabled, then logs/spans will be ignored.
components to prevent telemetry from itself being fed back into OTel.
BatchLogProcessor
,BatchSpanProcessor
, andPeriodicReader
modified to setthe suppression flag in their dedicated thread, so that telemetry generated from
those threads will not be fed back into OTel.
SimpleLogProcessor
also modified to suppress telemetry before invoking exporters.
Feature: Implemented and enabled cardinality capping for Metrics by
default. #2901
configurability but has now been reintroduced with the ability to configure
the limit.
true
instead of the string
"true"
.#2878
The
shutdown_with_timeout
method is added to SpanProcessor, SpanExporter trait and TracerProvider.The
shutdown_with_timeout
method is added to LogExporter trait.The
shutdown_with_timeout
method is added to LogProvider and LogProcessor trait.Breaking
MetricError
,MetricResult
no longer public (except whenspec_unstable_metrics_views
feature flag is enabled).OTelSdkResult
shouldbe used instead, wherever applicable. #2906
Breaking change, affecting custom
MetricReader
authors:shutdown_with_timeout
method is added toMetricReader
trait.collect
method on
MetricReader
modified to returnOTelSdkResult
.#2905
MetricReader
trait,
ManualReader
struct,Pipeline
struct,InstrumentKind
enum movedbehind feature flag "experimental_metrics_custom_reader".
#2928
Views improvements:
name, unit, description, and cardinality limit of a metric via views without
enabling the
spec_unstable_metrics_views
feature flag. Advanced viewfeatures, such as custom aggregation or attribute filtering, still require
the
spec_unstable_metrics_views
feature.new_view()
method andView
trait. Views can now be added by passinga function with signature
Fn(&Instrument) -> Option<Stream>
to thewith_view
method on
MeterProviderBuilder
.Introduced a builder pattern for
Stream
creation to use with views:StreamBuilder
struct with methods to configure stream propertiesStream::builder()
method that returns a newStreamBuilder
StreamBuilder::build()
returnsResult<Stream, Box<dyn Error>>
enablingproper validation.
Example of using views to rename a metric:
Aggregation
enum moved behind feature flag"spec_unstable_metrics_views". This was only required when using advanced view
capabilities.
#2928
PushMetricExporter
authors:export
method onPushMetricExporter
now accepts&ResourceMetrics
instead of
&mut ResourceMetrics
.ResourceMetrics
no longer exposesscope_metrics
field, but insteadoffers
scope_metrics()
method that returns an iterator over the same.ScopeMetrics
no longer exposesmetrics
field, but instead offersmetrics()
method that returns an iterator over the same.Sum
,Gauge
,Histogram
&ExponentialHistogram
no longer exposesdata_points
field, but instead offersdata_points()
method that returnsan iterator over the same.
SumDataPoint
,GaugeDataPoint
,HistogramDataPoint
&ExponentialHistogramDataPoint
no longer exposesattributes
,exemplars
field, but instead offers
attributes()
, andexemplars()
method thatreturns an iterator over the same.
Exemplar
no longer exposesfiltered_attributes
field, but insteadoffers
filtered_attributes()
method that returns an iterator overthe same.
HistogramDataPoint
no longer exposesbounds
andbucket_counts
, butinstead offers
bounds()
andbucket_counts()
methods that returns aniterator over the same.
Metric
no longer exposesname
,description
,unit
,data
fields, butinstead offers
name()
,description()
,unit()
, anddata()
accessor methods.ResourceMetrics
no longer exposesresource
field, but instead offersa
resource()
accessor method.ScopeMetrics
no longer exposesscope
field, but instead offersa
scope()
accessor method.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.
🔕 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.