fix(deps): update module go.opentelemetry.io/collector/pdata to v1.35.0 (main) #18284
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:
v1.34.0
->v1.35.0
Release Notes
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/pdata)
v1.35.0
🛑 Breaking changes 🛑
exporterhelper
: Remove deprecated sending_queue::blocking options, use sending_queue::block_on_overflow. (#13211)💡 Enhancements 💡
mdatagen
: Taught mdatagen to print thego list
stderr output on failures, and to rungo list
where the metadata file is. (#13205)service
: Support settingsampler
andlimits
underservice::telemetry::traces
(#13201)This allows users to enable sampling and set span limits on internal Collector traces using the
OpenTelemetry SDK declarative configuration.
pdata/pprofile
: Add new helper methodsFromLocationIndices
andPutLocation
to read and modify the content of locations. (#13150)exporterhelper
: Preserve request span context and client information in the persistent queue. (#11740, #13220, #13232)It allows internal collector spans and client information to propagate through the persistent queue used by
the exporters. The same way as it's done for the in-memory queue.
Currently, it is behind the exporter.PersistRequestContext feature gate, which can be enabled by adding
--feature-gates=exporter.PersistRequestContext
to the collector command line. An exporter buffer stored bya previous version of the collector (or by a collector with the feature gate disabled) can be read by a newer
collector with the feature enabled. However, the reverse is not supported: a buffer stored by a newer collector with
the feature enabled cannot be read by an older collector (or by a collector with the feature gate disabled).
🧰 Bug fixes 🧰
pdata
: Fix copying of optional fields when the source is unset. (#13268)service
: Only allocate one set of internal log sampling counters (#13014)The case where logs are only exported to stdout was fixed in v0.126.0;
this new fix also covers the case where logs are exported through OTLP.
Configuration
📅 Schedule: 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.