t.behrendt/tracebasedlogsampler
1
0
Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Releases Activity

chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.152.0 #67

Merged
t.behrendt merged 1 commits from renovate/go.opentelemetry.io-collector-processor-processortest-0.x into main 2026-05-19 10:38:19 +02:00
Conversation 2 Commits 1 Files Changed 2
+12 -4
renovate-bot commented 2026-05-16 12:19:32 +02:00
Collaborator
Copy Link
Copy Source

This PR contains the following updates:

Package Change Age Confidence
go.opentelemetry.io/collector/processor/processortest v0.151.0 → v0.152.0 age confidence

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/processor/processortest)

v0.152.0

Compare Source

💡 Enhancements 💡
  • pkg/exporterhelper: Add otelcol_exporter_in_flight_requests metric to track the number of export requests currently in-flight per exporter. (#​15009)
    This UpDownCounter increments in startOp and decrements in endOp, allowing operators to monitor
    concurrent export activity and detect when an exporter is saturating its worker pool.
🧰 Bug fixes 🧰

  • pkg/confighttp: Close the original request body after reading block-format Content-Encoding: snappy requests. (#​15262)

  • pkg/confighttp: Recover from panics in decompression libraries, return HTTP 400 instead of 500. (#​13228)

  • pkg/confighttp: Enforce max_request_body_size on Content-Encoding: snappy requests before the decoded buffer is allocated. (#​15252)

  • pkg/otelcol: Stop emitting verbose gRPC transport messages at WARN during normal client disconnect. (#​5169)
    grpc-go gates chatty per-RPC notices (e.g. "HandleStreams failed to read frame:
    connection reset by peer") behind LoggerV2.V(2). zapgrpc.Logger.V conflates
    grpclog verbosity with zap severity, so V(2) returns true whenever WARN is
    enabled and these messages emit at WARN. Wrap the installed grpclog.LoggerV2
    with a corrected V() that compares against a fixed verbosity threshold,
    matching grpclog's intended semantics. See uber-go/zap#1544.

  • pkg/pdata: pcommon.Value.AsString no longer HTML-escapes <, >, and & inside ValueTypeMap and ValueTypeSlice values, matching the behavior already used for ValueTypeStr. (#​14662)

  • pkg/service: Fix Prometheus config defaults mismatch when host is explicitly set in telemetry configuration. (#​13867)
    When users explicitly configured the telemetry metrics section (e.g. to change the host),
    the Prometheus exporter boolean fields (WithoutScopeInfo, WithoutUnits, WithoutTypeSuffix)
    defaulted to nil/false instead of true, causing metric name format changes compared to the
    implicit default configuration. This fix applies the correct defaults during config unmarshaling.

  • pkg/service: Return noop tracer provider when no trace processors are defined (#​15135)

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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [go.opentelemetry.io/collector/processor/processortest](https://github.com/open-telemetry/opentelemetry-collector) | `v0.151.0` → `v0.152.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/go.opentelemetry.io%2fcollector%2fprocessor%2fprocessortest/v0.152.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/go.opentelemetry.io%2fcollector%2fprocessor%2fprocessortest/v0.151.0/v0.152.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/processor/processortest)</summary> ### [`v0.152.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1580v01520) [Compare Source](https://github.com/open-telemetry/opentelemetry-collector/compare/v0.151.0...v0.152.0) ##### 💡 Enhancements 💡 - `pkg/exporterhelper`: Add `otelcol_exporter_in_flight_requests` metric to track the number of export requests currently in-flight per exporter. ([#&#8203;15009](https://github.com/open-telemetry/opentelemetry-collector/issues/15009)) This UpDownCounter increments in startOp and decrements in endOp, allowing operators to monitor concurrent export activity and detect when an exporter is saturating its worker pool. ##### 🧰 Bug fixes 🧰 - `pkg/confighttp`: Close the original request body after reading block-format `Content-Encoding: snappy` requests. ([#&#8203;15262](https://github.com/open-telemetry/opentelemetry-collector/issues/15262)) - `pkg/confighttp`: Recover from panics in decompression libraries, return HTTP 400 instead of 500. ([#&#8203;13228](https://github.com/open-telemetry/opentelemetry-collector/issues/13228)) - `pkg/confighttp`: Enforce `max_request_body_size` on `Content-Encoding: snappy` requests before the decoded buffer is allocated. ([#&#8203;15252](https://github.com/open-telemetry/opentelemetry-collector/issues/15252)) - `pkg/otelcol`: Stop emitting verbose gRPC transport messages at WARN during normal client disconnect. ([#&#8203;5169](https://github.com/open-telemetry/opentelemetry-collector/issues/5169)) grpc-go gates chatty per-RPC notices (e.g. "HandleStreams failed to read frame: connection reset by peer") behind `LoggerV2.V(2)`. zapgrpc.Logger.V conflates grpclog verbosity with zap severity, so V(2) returns true whenever WARN is enabled and these messages emit at WARN. Wrap the installed grpclog.LoggerV2 with a corrected V() that compares against a fixed verbosity threshold, matching grpclog's intended semantics. See [uber-go/zap#1544](https://github.com/uber-go/zap/issues/1544). - `pkg/pdata`: `pcommon.Value.AsString` no longer HTML-escapes `<`, `>`, and `&` inside `ValueTypeMap` and `ValueTypeSlice` values, matching the behavior already used for `ValueTypeStr`. ([#&#8203;14662](https://github.com/open-telemetry/opentelemetry-collector/issues/14662)) - `pkg/service`: Fix Prometheus config defaults mismatch when host is explicitly set in telemetry configuration. ([#&#8203;13867](https://github.com/open-telemetry/opentelemetry-collector/issues/13867)) When users explicitly configured the telemetry metrics section (e.g. to change the host), the Prometheus exporter boolean fields (WithoutScopeInfo, WithoutUnits, WithoutTypeSuffix) defaulted to nil/false instead of true, causing metric name format changes compared to the implicit default configuration. This fix applies the correct defaults during config unmarshaling. - `pkg/service`: Return noop tracer provider when no trace processors are defined ([#&#8203;15135](https://github.com/open-telemetry/opentelemetry-collector/issues/15135)) <!-- previous-version --> </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My41LjQiLCJ1cGRhdGVkSW5WZXIiOiI0My41LjQiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
renovate-bot commented 2026-05-16 12:19:32 +02:00
Author
Collaborator
Copy Link
Copy Source

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 3 additional dependencies were updated

Details:

Package Change
go.opentelemetry.io/collector/component/componentstatus v0.151.0 -> v0.152.0
go.opentelemetry.io/collector/processor/xprocessor v0.151.0 -> v0.152.0
go.opentelemetry.io/collector/component/componenttest v0.151.0 -> v0.152.0
### ℹ️ Artifact update notice ##### File name: go.mod In order to perform the update(s) described in the table above, Renovate ran the `go get` command, which resulted in the following additional change(s): - 3 additional dependencies were updated Details: | **Package** | **Change** | | :-------------------------------------------------------- | :----------------------- | | `go.opentelemetry.io/collector/component/componentstatus` | `v0.151.0` -> `v0.152.0` | | `go.opentelemetry.io/collector/processor/xprocessor` | `v0.151.0` -> `v0.152.0` | | `go.opentelemetry.io/collector/component/componenttest` | `v0.151.0` -> `v0.152.0` |
renovate-bot added 1 commit 2026-05-19 10:36:47 +02:00
chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.152.0
renovate/stability-days Updates have met minimum release age requirement
Details
CI / test (push) Successful in 12s
Details
c080126b44
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-processor-processortest-0.x from 3f31df84b8 to c080126b44 2026-05-19 10:36:47 +02:00 Compare
t.behrendt approved these changes 2026-05-19 10:38:17 +02:00
t.behrendt merged commit 795e96270a into main 2026-05-19 10:38:19 +02:00
t.behrendt deleted branch renovate/go.opentelemetry.io-collector-processor-processortest-0.x 2026-05-19 10:38:19 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
t.behrendt
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
branch-buddy renovate-bot trivy-bot t.behrendt
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t.behrendt/tracebasedlogsampler#67
Delete Branch "renovate/go.opentelemetry.io-collector-processor-processortest-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?