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 to v1.55.0 - autoclosed #48

Closed
renovate-bot wants to merge 1 commits from renovate/go.opentelemetry.io-collector-processor-1.x into main
pull from: renovate/go.opentelemetry.io-collector-processor-1.x
merge into: t.behrendt:main
Conversation 1 Commits 1 Files Changed 2 +35 -12
renovate-bot commented 2026-04-07 12:18:28 +02:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Confidence
go.opentelemetry.io/collector/processor v1.54.0 → v1.55.0 age confidence

Release Notes

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

v1.55.0

🛑 Breaking changes 🛑
  • pkg/service: Remove service_name, service_instance_id, and service_version as constant labels on every internal metric datapoint. These attributes are already present in target_info and were being duplicated on each series for OpenCensus backwards compatibility. (#​14811)
    Previously, the collector stamped every internal metric series (e.g. otelcol_process_runtime_heap_alloc_bytes)
    with service_name, service_instance_id, and service_version labels to match the old OpenCensus behavior.
    These attributes are now only present in the target_info metric, which is the correct Prometheus/OTel convention.
    Users who filter or group by these labels on individual metrics will need to update their queries to use
    target_info joins instead.
💡 Enhancements 💡

  • all: Move aix/ppc64 to tier 3 support (#​13380)

  • all: Upgrade the profiles stability status to alpha (#​14817)
    The following components have their profiles status upgraded from development to alpha:

    • pdata/pprofile
    • connector/forward
    • exporter/debug
    • receiver/nop
    • exporter/nop
    • exporter/otlp_grpc
    • exporter/otlp_http

  • cmd/mdatagen: Add semconv reference for attributes (#​13297)

🧰 Bug fixes 🧰
  • cmd/mdatagen: Fix entity code generation so extra_attributes are emitted as resource attributes instead of entity descriptive attributes. (#​14778)

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](https://github.com/open-telemetry/opentelemetry-collector) | `v1.54.0` → `v1.55.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/go.opentelemetry.io%2fcollector%2fprocessor/v1.55.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/go.opentelemetry.io%2fcollector%2fprocessor/v1.54.0/v1.55.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/processor)</summary> ### [`v1.55.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1550v01490) ##### 🛑 Breaking changes 🛑 - `pkg/service`: Remove `service_name`, `service_instance_id`, and `service_version` as constant labels on every internal metric datapoint. These attributes are already present in `target_info` and were being duplicated on each series for OpenCensus backwards compatibility. ([#&#8203;14811](https://github.com/open-telemetry/opentelemetry-collector/issues/14811)) Previously, the collector stamped every internal metric series (e.g. `otelcol_process_runtime_heap_alloc_bytes`) with `service_name`, `service_instance_id`, and `service_version` labels to match the old OpenCensus behavior. These attributes are now only present in the `target_info` metric, which is the correct Prometheus/OTel convention. Users who filter or group by these labels on individual metrics will need to update their queries to use `target_info` joins instead. ##### 💡 Enhancements 💡 - `all`: Move aix/ppc64 to tier 3 support ([#&#8203;13380](https://github.com/open-telemetry/opentelemetry-collector/issues/13380)) - `all`: Upgrade the profiles stability status to alpha ([#&#8203;14817](https://github.com/open-telemetry/opentelemetry-collector/issues/14817)) The following components have their profiles status upgraded from development to alpha: - pdata/pprofile - connector/forward - exporter/debug - receiver/nop - exporter/nop - exporter/otlp\_grpc - exporter/otlp\_http - `cmd/mdatagen`: Add semconv reference for attributes ([#&#8203;13297](https://github.com/open-telemetry/opentelemetry-collector/issues/13297)) ##### 🧰 Bug fixes 🧰 - `cmd/mdatagen`: Fix entity code generation so `extra_attributes` are emitted as resource attributes instead of entity descriptive attributes. ([#&#8203;14778](https://github.com/open-telemetry/opentelemetry-collector/issues/14778)) <!-- 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 added 1 commit 2026-04-07 12:18:28 +02:00
chore(deps): update module go.opentelemetry.io/collector/processor to v1.55.0
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
CI / test (push) Successful in 35s
Details
21547d29a0
renovate-bot commented 2026-04-07 12:18:28 +02:00
Author
Collaborator
Copy Link

ℹ️ 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):

  • 11 additional dependencies were updated

Details:

Package Change
go.opentelemetry.io/collector/consumer/xconsumer v0.148.0 -> v0.149.0
go.opentelemetry.io/collector/featuregate v1.54.0 -> v1.55.0
go.opentelemetry.io/collector/internal/componentalias v0.148.0 -> v0.149.0
go.opentelemetry.io/collector/pdata/pprofile v0.148.0 -> v0.149.0
go.opentelemetry.io/collector/pdata/testdata v0.148.0 -> v0.149.0
go.opentelemetry.io/collector/pipeline v1.54.0 -> v1.55.0
google.golang.org/grpc v1.79.2 -> v1.79.3
go.opentelemetry.io/collector/component v1.54.0 -> v1.55.0
go.opentelemetry.io/collector/consumer v1.54.0 -> v1.55.0
go.opentelemetry.io/collector/consumer/consumertest v0.148.0 -> v0.149.0
go.opentelemetry.io/collector/pdata v1.54.0 -> v1.55.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): - 11 additional dependencies were updated Details: | **Package** | **Change** | | :------------------------------------------------------ | :----------------------- | | `go.opentelemetry.io/collector/consumer/xconsumer` | `v0.148.0` -> `v0.149.0` | | `go.opentelemetry.io/collector/featuregate` | `v1.54.0` -> `v1.55.0` | | `go.opentelemetry.io/collector/internal/componentalias` | `v0.148.0` -> `v0.149.0` | | `go.opentelemetry.io/collector/pdata/pprofile` | `v0.148.0` -> `v0.149.0` | | `go.opentelemetry.io/collector/pdata/testdata` | `v0.148.0` -> `v0.149.0` | | `go.opentelemetry.io/collector/pipeline` | `v1.54.0` -> `v1.55.0` | | `google.golang.org/grpc` | `v1.79.2` -> `v1.79.3` | | `go.opentelemetry.io/collector/component` | `v1.54.0` -> `v1.55.0` | | `go.opentelemetry.io/collector/consumer` | `v1.54.0` -> `v1.55.0` | | `go.opentelemetry.io/collector/consumer/consumertest` | `v0.148.0` -> `v0.149.0` | | `go.opentelemetry.io/collector/pdata` | `v1.54.0` -> `v1.55.0` |
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/processor to v1.55.0 to chore(deps): update module go.opentelemetry.io/collector/processor to v1.55.0 - autoclosed 2026-04-07 15:53:41 +02:00
renovate-bot closed this pull request 2026-04-07 15:53:41 +02:00
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
CI / test (push) Successful in 35s
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
branch-buddy renovate-bot trivy-bot t.behrendt
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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