fix(deps): update opentelemetry-rust monorepo #2443
+13
−13
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.23.0
->0.24.0
0.4.0
->0.5.0
0.12.0
->0.13.0
0.16.0
->0.17.0
0.16.0
->0.17.0
0.15.0
->0.16.0
0.4.0
->0.5.0
0.23.0
->0.24.0
Release Notes
open-telemetry/opentelemetry-rust (opentelemetry)
v0.24.0
Compare Source
See individual crate changelogs for details.
open-telemetry/opentelemetry-rust (opentelemetry-appender-tracing)
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.
Update
opentelemetry
dependency version to 0.24open-telemetry/opentelemetry-rust (opentelemetry-otlp)
v0.17.0
Compare 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_resource
onOtlpLogPipeline
, replacing thewith_config
method.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 returnTracerProvider
instead 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.
target
fromLogRecord
, if target is populated.LogRecord
andSpan
by their resource and instrumentation scope before exporting, for better efficiency #1873.http
v1 andtonic
v0.12 #1674opentelemetry
dependency version to 0.24opentelemetry_sdk
dependency version to 0.24opentelemetry-http
dependency version to 0.13opentelemetry-proto
dependency version to 0.7open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)
v0.16.0
Compare Source
Changed
opentelemetry_semantic_conventions::trace
andopentelemetry_semantic_conventions::resource
intoopentelemetry_semantic_conventions::attribute
(which now contains all semantic attributes).trace
andresource
now only contain references to attributes which fall under their respective category.Added
opentelemetry_semantic_conventions::metric
to store metric semantic conventions.open-telemetry/opentelemetry-rust (opentelemetry-stdout)
v0.5.0
Compare Source
opentelemetry
dependency version to 0.24opentelemetry_sdk
dependency version to 0.24Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.