fix(deps): update module go.opentelemetry.io/collector/pdata to v1.28.0 #6461
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.27.0
->v1.28.0
Release Notes
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/pdata)
v1.28.0
🛑 Breaking changes 🛑
service
: Batch processor telemetry is no longer emitted at "basic" verbosity level (#7890)According to the guidelines, basic-level telemetry should be reserved for core Collector APIs.
Components such as the batch processor should emit telemetry starting from the "normal" level
(which is also the default level).
Migration: If your Collector telemetry was set to
level: basic
and you want to keep seeingbatch processor-related metrics, consider switching to
level: normal
instead.💡 Enhancements 💡
service
: Addservice.AllowNoPipelines
feature gate to allow starting the Collector without pipelines. (#12613)This can be used to start with only extensions.
mdatagen
: Delete generated_status.go if the component type doesn't require it. (#12346)componenttest
: Improve config struct mapstructure field tag checks (#12590)remain
tags andomitempty
tags without a custom field name will now pass validation.service
: include component id/type in start error (#10426)mdatagen
: Add deprecation date and migration guide fields as part of component metadata (#12359)confmap
: Introduce a new feature flag to allow for merging lists instead of discarding the existing ones. (#8394, #8754, #10370)You can enable this option via the command line by running following command:
otelcol --config=main.yaml --config=extra_config.yaml --feature-gates=-confmap.enableMergeAppendOption
zpagesextension
: Add expvar handler to zpages extension. (#11081)🧰 Bug fixes 🧰
confmap
: Maintain nil values when marshaling or unmarshaling nil slices (#11882)Previously, nil slices were converted to empty lists, which are semantically different
than a nil slice. This change makes this conversion more consistent when encoding
or decoding config, and these values are now maintained.
service
: do not attempt to register process metrics if they are disabled (#12098)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 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.