This repository was archived by the owner on Nov 20, 2025. It is now read-only.
fix(deps): update module go.opentelemetry.io/collector/component to v0.120.0 #54
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:
v0.115.0->v0.120.0Release Notes
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/component)
v0.120.0Compare Source
🛑 Breaking changes 🛑
all: Added support for go1.24, bumped minimum version to 1.23 (#12370)mdatagen: Removing deprecated generated funcs and a few test funcs as well. (#12304)service: Align component logger attributes with those defined in RFC (#12217)See Pipeline Component Telemetry RFC
💡 Enhancements 💡
otlpreceiver: Update stability for logs (#12335)exporterhelper: Implement sync disabled queue used when batching is enabled. (#12245)exporterhelper: Enable the new pull-based batcher in exporterhelper (#12291)exporterhelper: Update queue size after the element is done exported (#12399)After this change the active queue size will include elements in the process of being exported.
otelcol: Add featuregate command to display information about available features (#11998)The featuregate command allows users to view detailed information about feature gates
including their status, stage, and description.
🧰 Bug fixes 🧰
memorylimiter: Logger no longer attributes to single signal, pipeline, or component. (#12217)otlpreceiver: Logger no longer attributes to random signal when receiving multiple signals. (#12217)exporterhelper: Fix undefined behavior access to request after send to next component. This causes random memory access. (#12281)exporterhelper: Fix default batcher to correctly call all done callbacks exactly once (#12247)otlpreceiver: Fix OTLP http receiver to correctly set Retry-After (#12367)otlphttpexporter: Fix parsing logic for Retry-After in OTLP http protocol. (#12366)The value of Retry-After field can be either an HTTP-date or delay-seconds and the current logic only parsed delay-seconds.
cmd/builder: Ensure unique aliases for modules with same suffix (#12201)v0.119.0Compare Source
🛑 Breaking changes 🛑
exporterhelper: Rename exporter span signal specific attributes (e.g. "sent_spans" / "send_failed_span") to "items.sent" / "items.failed". (#12165)cmd/mdatagen: Remove dead fieldtelemetry::level(#12144)exporterhelper: Change exporter ID to be a Span level attribute instead on each event. (#12164)This does not have an impact on the level of information emitted, but on the structure of the Span.
cmd/mdatagen: Removelevelfield from metrics definition (#12145)This mechanism will be added back once a new views mechanism is implemented.
service: Value for telemetry exporterotlp.protocolupdated fromgrpc/protobuftogrpc. (#12337)service: internal metrics exported over Prometheus may differ from previous versions. (#11611)Users who do not customize the Prometheus reader should not be impacted. The change to update the internal telemetry to use otel-go config can cause unexpected behaviour
for end users. This change is caused by the default values in
configbeing different from what the Collector has used in previous versions. Thefollowing changes can occur when users configure their
service::telemetry::metrics::readers:_totalsuffix ifwithout_type_suffixis not configured. Setwithout_type_suffixtotrueto disable this.without_unitsis not configured. Setwithout_unitstotrueto disable this.target_infometric will be emitted ifwithout_scope_infois not configured. Setwithout_scope_infototrueto disable this.💡 Enhancements 💡
configtls: Allow users to mention their preferred curve types for ECDHE handshake (#12174)service: remove custom code and instead use config package to instantiate meter provider. (#11611)otelcol: Adds support for listing config providers in components command's output (#11570)general: Reduce memory allocations when loading configuration and parsing component names (#11964)🧰 Bug fixes 🧰
exporterhelper: Fix bug that the exporter with new batcher may have been marked as non mutation. (#12239)Only affects users that manually turned on
exporter.UsePullingBasedExporterQueueBatcherfeaturegate.service: Preserve URL normalization logic that was present before. (#12254)confighttp: confighttp.ToServer now sets ErrorLog with a default logger backed by Zap (#11820)This change ensures that the http.Server's ErrorLog is correctly set using Zap's logger at the error level, addressing the issue of error logs being printed using a different logger.
exporterhelper: Fix context propagation for DisabledBatcher (#12231)mdatagen: apply fieldalignment to generated code (#12125)mdatagen: Fix bug where Histograms were marked as not supporting temporal aggregation (#12168)exporterhelper: Fix MergeSplit issue that ignores the initial message size. (#12257)service: Include validation errors from telemetry.Config when validating the service config (#12100)Previously validation errors were only printed to the console
service-telemetry: pass the missing async error channel into service telemetry settings (#11417)v0.118.0Compare Source
💡 Enhancements 💡
exporterhelper: Add blocking option to control queue behavior when full (#12090)debugexporter: Add EventName to debug exporter for Logs. EventName was added as top-level field in the LogRecord from 1.5.0 of proto definition. (#11966)confighttp: Added support for configuring compression levels. (#10467)A new configuration option called CompressionParams has been added to confighttp. | This allows users to configure the compression levels for the confighttp client.
exporterhelper: Change the memory queue implementation to not pre-allocate capacity objects. (#12070)This change improves memory usage of the collector under low utilization and is a prerequisite for supporting different other size limitations (number of items, bytes).
🧰 Bug fixes 🧰
mdatagen: apply fieldalignment to generated code (#12121)otelcoltest: SetDefaultSchemetoenvin the testConfigProviderto replicate the default provider used by the Collector. (#12066)v0.117.0Compare Source
🛑 Breaking changes 🛑
otelcol: Remove warnings when 0.0.0.0 is used (#11713, #8510)🧰 Bug fixes 🧰
internal/sharedcomponent: Fixed bug where sharedcomponent would use too much memory remembering all the previously reported statuses (#11826)v0.116.0Compare Source
🛑 Breaking changes 🛑
pdata/pprofile: Remove deprecatedProfile.EndTimeandProfile.SetEndTimemethods. (#11796)💡 Enhancements 💡
xconfighttp: Add WithOtelHTTPOptions to experimental module xconfighttp (#11770)🧰 Bug fixes 🧰
exporterhelper: Fix memory leak at exporter shutdown (#11401)sharedcomponent: Remove race-condition and cleanup locking (#11819)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 this update again.
This PR was generated by Mend Renovate. View the repository job log.