fix(deps): update module go.opentelemetry.io/collector/pdata to v1.31.0 #6707
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.30.0
->v1.31.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/pdata)
v1.31.0
🛑 Breaking changes 🛑
service
: Lowercase values for 'otelcol.component.kind' attributes. (#12865)service
: Restrict thetelemetry.newPipelineTelemetry
feature gate to metrics. (#12856, #12933)The "off" state of this feature gate introduced a regression, where the Collector's internal logs were missing component attributes. See issue #12870 for more details on this bug.
On the other hand, the "on" state introduced an issue with the Collector's default internal metrics, because the Prometheus exporter does not currently support instrumentation scope attributes.
To solve both of these issues, this change turns on the new scope attributes for logs and traces by default regardless of the feature gate.
However, the new scope attributes for metrics stay locked behind the feature gate, and will remain off by default until the Prometheus exporter is updated to support scope attributes.
Please understand that enabling the
telemetry.newPipelineTelemetry
feature gate may break the export of Collector metrics through, depending on your configuration.Having a
batch
processor in multiple pipelines is a known trigger for this.This comes with a breaking change, where internal logs exported through OTLP will now use instrumentation scope attributes to identify the source component instead of log attributes.
This does not affect the Collector's stderr output. See the changelog for v0.123.0 for a more detailed description of the gate's effects.
💡 Enhancements 💡
mdatagen
: Add support for attributes for telemetry configuration in metadata. (#12919)configmiddleware
: Add extensionmiddleware interface. (#12603, #9591)configgrpc
: Add gRPC middleware support. (#12603, #9591)confighttp
: Add HTTP middleware support. (#12603, #9591, #7441)configmiddleware
: Add configmiddleware struct. (#12603, #9591)🧰 Bug fixes 🧰
exporterhelper
: Do not ignore thenum_consumers
setting when batching is enabled. (#12244)exporterhelper
: Reject elements larger than the queue capacity (#12847)mdatagen
: Add time and plog package imports (#12907)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.
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.