generated from template/go
fix(deps): update module go.opentelemetry.io/collector/connector to v0.156.0 - autoclosed #28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/go.opentelemetry.io-collector-connector-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v0.155.0→v0.156.0Release Notes
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/connector)
v0.156.0Compare Source
💡 Enhancements 💡
cmd/mdatagen: Add support for defining stability levels for resource attributes (#15312)cmd/mdatagen: Add semantic convention reference to resource attributes (#15313)processor/memory_limiter: Adding health events for the memorylimiter (#14700)Publish health event from memorylimiter using componentstatus.ReportStatus
🧰 Bug fixes 🧰
cmd/mdatagen: Removes the extra line in the documentation.md between extended description and table (#15458)exporter/otlp_http: Treat errors parsing successful (2xx) HTTP response bodies as permanent errors to prevent retrying already-accepted data. (#15386)When a server returns a 2xx status but the response body exceeds the 64kB read limit,
the body is truncated and proto unmarshaling fails. Previously this was treated as a
retryable error, causing duplicate data to be exported. Now it is marked as a permanent
error so the retry logic will not re-send data that was already accepted by the server.
pkg/config/configretry: Always validate BackOffConfig fields regardless of the Enabled flag. (#15437)pkg/service: Ensure receivers always start after all other components (#15495)There was previously a race condition where multiple receivers using a shared internal implementation,
such as the OTLP receiver, could start sending telemetry into a pipeline before all its components had fully started.
processor/memory_limiter: Fix degenerate collector performance when exporter has problems causing permanent CPU-burning GC loop (#4981)Forced GC runs now use exponential backoff when deemed ineffective
(still above soft limit and less than 5% reclaimed) to avoid preventing
recovery by overloading CPU with excessive GC runs. The cap on the
backoff interval is exposed via
max_gc_interval_when_soft_limitedandmax_gc_interval_when_hard_limited(both default30s); set either to0to disable backoff on that path.provider/env: Fix empty env var default resolving to nil instead of empty string (#14587)When using ${env:VAR:-} with an unset variable, the empty default now correctly
resolves to an empty string instead of nil.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate.
ℹ️ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the
go getcommand, which resulted in the following additional change(s):Details:
go.opentelemetry.io/collector/consumerv1.61.0->v1.62.0go.opentelemetry.io/collector/consumer/consumertestv0.155.0->v0.156.0go.opentelemetry.io/collector/consumer/xconsumerv0.155.0->v0.156.0go.opentelemetry.io/collector/internal/componentaliasv0.155.0->v0.156.0go.opentelemetry.io/collector/internal/fanoutconsumerv0.155.0->v0.156.0go.opentelemetry.io/collector/pdata/pprofilev0.155.0->v0.156.0go.opentelemetry.io/collector/pdata/testdatav0.155.0->v0.156.0go.opentelemetry.io/collector/pipelinev1.61.0->v1.62.0972a5055bad9d8893f07fix(deps): update module go.opentelemetry.io/collector/connector to v0.156.0to fix(deps): update module go.opentelemetry.io/collector/connector to v0.156.0 - autoclosedPull request closed