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/confmap to v1.54.0 #33

Merged
t.behrendt merged 1 commits from renovate/go.opentelemetry.io-collector-confmap-1.x into main 2026-03-26 21:22:50 +01:00
Conversation 2 Commits 1 Files Changed 2 +6 -2
renovate-bot commented 2026-02-15 00:27:01 +01:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Confidence
go.opentelemetry.io/collector/confmap v1.50.0 → v1.54.0 age confidence

Release Notes

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

v1.54.0

❗ Known Issues ❗
  • service: The collector's internal Prometheus metrics endpoint (:8888) now emits OTel service labels with underscore
    names (service_name, service_instance_id, service_version) instead of dot-notation names (service.name,
    service.instance.id, service.version). Users scraping this endpoint with the Prometheus receiver will see these renamed
    labels in resource and datapoint attributes. As a workaround, add the following metric_relabel_configs to your scrape
    config in prometheus receiver: 
    metric_relabel_configs:
  - source_labels: [service_name]
    target_label: service.name
  - source_labels: [service_instance_id]
    target_label: service.instance.id
  - source_labels: [service_version]
    target_label: service.version
  - regex: service_name|service_instance_id|service_version
    action: labeldrop
    See #​14814 for details and updates.
🛑 Breaking changes 🛑
  • all: Change metric units to be singular to match OTel specification, e.g. {requests} -> {request} (#​14753)
💡 Enhancements 💡
  • cmd/mdatagen: Add deprecated_type field to allow specifying an alias for component types. (#​14718)
  • cmd/mdatagen: Generate entity-scoped MetricsBuilder API that enforces entity-metric associations at compile time (#​14659)
  • cmd/mdatagen: Skip generating reaggregation config options for metrics that have no aggregatable attributes. (#​14689)
  • pkg/service: The internal status reporter no longer drops repeated Ok and RecoverableError statuses (#​14282)
    Status events can now carry metadata and there's value in allowing them to be emitted despite the status value itself
    not changing.
🧰 Bug fixes 🧰

  • cmd/builder: Add .exe to output binary names when building for Windows targets. (#​12591)

  • exporter/debug: Add printing of metric metadata in detailed verbosity. (#​14667)

  • exporter/otlp_grpc: Prevent nil pointer panic when push methods are called before the OTLP exporter initializes its gRPC clients. (#​14663)
    When the sending queue and retry are disabled, calling ConsumeTraces,
    ConsumeMetrics, ConsumeLogs, or ConsumeProfiles before the OTLP exporter
    initializes its gRPC clients could cause a nil pointer dereference panic.
    The push methods now return an error instead of panicking.

  • exporter/otlp_http: Show the actual destination URL in error messages when request URL is modified by middleware. (#​14673)
    Unwraps the *url.Error returned by http.Client.Do() to prevent misleading error logs when a middleware extension dynamically updates the endpoint.

  • pdata/pprofile: Switch the dictionary of dictionary tables entries only once when merging profiles (#​14709)
    For dictionary table data, we used to switch their dictionaries when doing
    the switch for the data that uses them.
    However, when an entry is associated with multiple other data (several
    samples can use the same stack), we would have been switching the
    dictionaries of the entry multiple times.

    We now switch dictionaries for dictionary table data only once, before
    switching the resource profiles.

v1.53.0

💡 Enhancements 💡
  • exporter/debug: Output bucket counts for exponential histogram data points in normal verbosity. (#​10463)
  • pkg/exporterhelper: Add metadata_keys configuration to sending_queue.batch.partition to partition batches by client metadata (#​14139)
    The metadata_keys configuration option is now available in the sending_queue.batch.partition section for all exporters.
    When specified, batches are partitioned based on the values of the listed metadata keys, allowing separate batching per metadata partition. This feature
    is automatically configured when using exporterhelper.WithQueue().
🧰 Bug fixes 🧰

  • cmd/builder: Fix duplicate error output when CLI command execution fails in the builder tool. (#​14436)

  • cmd/mdatagen: Fix duplicate error output when CLI command execution fails in the mdatagen tool. (#​14436)

  • cmd/mdatagen: Fix semconv URL validation for metrics with underscores in their names (#​14583)
    Metrics like system.disk.io_time now correctly validate against semantic convention URLs containing underscores in the anchor tag.

  • extension/memory_limiter: Use ChainUnaryInterceptor instead of UnaryInterceptor to allow multiple interceptors. (#​14634)
    If multiple extensions that use the UnaryInterceptor are set the binary panics at start time.

  • extension/memory_limiter: Add support for streaming services. (#​14634)

  • pkg/config/configmiddleware: Add context.Context to HTTP middleware interface constructors. (#​14523)
    This is a breaking API change for components that implement or use extensionmiddleware.

  • pkg/confmap: Fix another issue where configs could fail to decode when using interpolated values in string fields. (#​14034)
    For example, a resource attribute can be set via an environment variable to a string that is parseable as a number, e.g. 1234.

    (A similar bug was fixed in a previous release: that one was triggered when the field was nested in a struct,
    whereas this one is triggered when the field internally has type "pointer to string" rather than "string".)

  • pkg/otelcol: The featuregate subcommand now rejects extra positional arguments instead of silently ignoring them. (#​14554)

  • pkg/queuebatch: Fix data race in partition_batcher where resetTimer() was called outside mutex, causing concurrent timer.Reset() calls and unpredictable batch flush timing under load. (#​14491)

  • pkg/scraperhelper: Log scrapers now emit log-appropriate receiver telemetry (#​14654)
    Log scrapers previously emitted the same receiver telemetry as metric scrapers,
    such as the otelcol_receiver_accepted_metric_points metric (instead of otelcol_receiver_accepted_log_records),
    or spans named receiver/myreceiver/MetricsReceived (instead of receiver/myreceiver/LogsReceived).

    This did not affect scraper-specific spans and metrics.

  • processor/batch: Fixes a bug where the batch processor would not copy SchemaUrl metadata from resource and scope containers during partial batch splits. (#​12279, #​14620)

v1.52.0

v1.51.0

💡 Enhancements 💡
  • pkg/scraperhelper: ScraperID has been added to the logs for metrics, logs, and profiles (#​14461)
🧰 Bug fixes 🧰

  • exporter/otlp_grpc: Fix the OTLP exporter balancer to use round_robin by default, as intended. (#​14090)

  • pkg/config/configoptional: Fix Unmarshal methods not being called when config is wrapped inside Optional (#​14500)
    This bug notably manifested in the fact that the sending_queue::batch::sizer config for exporters
    stopped defaulting to sending_queue::sizer, which sometimes caused the wrong units to be used
    when configuring sending_queue::batch::min_size and max_size.

    As part of the fix, xconfmap exposes a new xconfmap.WithForceUnmarshaler option, to be used in the Unmarshal methods
    of wrapper types like configoptional.Optional to make sure the Unmarshal method of the inner type is called.

    The default behavior remains that calling conf.Unmarshal on the confmap.Conf passed as argument to an Unmarshal
    method will skip any top-level Unmarshal methods to avoid infinite recursion in standard use cases.

  • pkg/confmap: Fix an issue where configs could fail to decode when using interpolated values in string fields. (#​14413)
    For example, a header can be set via an environment variable to a string that is parseable as a number, e.g. 1234

  • pkg/service: Don't error on startup when process metrics are enabled on unsupported OSes (e.g. AIX) (#​14307)

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/confmap](https://github.com/open-telemetry/opentelemetry-collector) | `v1.50.0` → `v1.54.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/go.opentelemetry.io%2fcollector%2fconfmap/v1.54.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/go.opentelemetry.io%2fcollector%2fconfmap/v1.50.0/v1.54.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/confmap)</summary> ### [`v1.54.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1540v01480) ##### ❗ Known Issues ❗ - `service`: The collector's internal Prometheus metrics endpoint (`:8888`) now emits OTel service labels with underscore names (`service_name`, `service_instance_id`, `service_version`) instead of dot-notation names (`service.name`, `service.instance.id`, `service.version`). Users scraping this endpoint with the Prometheus receiver will see these renamed labels in resource and datapoint attributes. As a workaround, add the following `metric_relabel_configs` to your scrape config in prometheus receiver: ```yaml metric_relabel_configs: - source_labels: [service_name] target_label: service.name - source_labels: [service_instance_id] target_label: service.instance.id - source_labels: [service_version] target_label: service.version - regex: service_name|service_instance_id|service_version action: labeldrop ``` See [#&#8203;14814](https://github.com/open-telemetry/opentelemetry-collector/issues/14814) for details and updates. ##### 🛑 Breaking changes 🛑 - `all`: Change metric units to be singular to match OTel specification, e.g. `{requests}` -> `{request}` ([#&#8203;14753](https://github.com/open-telemetry/opentelemetry-collector/issues/14753)) ##### 💡 Enhancements 💡 - `cmd/mdatagen`: Add deprecated\_type field to allow specifying an alias for component types. ([#&#8203;14718](https://github.com/open-telemetry/opentelemetry-collector/issues/14718)) - `cmd/mdatagen`: Generate entity-scoped MetricsBuilder API that enforces entity-metric associations at compile time ([#&#8203;14659](https://github.com/open-telemetry/opentelemetry-collector/issues/14659)) - `cmd/mdatagen`: Skip generating reaggregation config options for metrics that have no aggregatable attributes. ([#&#8203;14689](https://github.com/open-telemetry/opentelemetry-collector/issues/14689)) - `pkg/service`: The internal status reporter no longer drops repeated Ok and RecoverableError statuses ([#&#8203;14282](https://github.com/open-telemetry/opentelemetry-collector/issues/14282)) Status events can now carry metadata and there's value in allowing them to be emitted despite the status value itself not changing. ##### 🧰 Bug fixes 🧰 - `cmd/builder`: Add `.exe` to output binary names when building for Windows targets. ([#&#8203;12591](https://github.com/open-telemetry/opentelemetry-collector/issues/12591)) - `exporter/debug`: Add printing of metric metadata in detailed verbosity. ([#&#8203;14667](https://github.com/open-telemetry/opentelemetry-collector/issues/14667)) - `exporter/otlp_grpc`: Prevent nil pointer panic when push methods are called before the OTLP exporter initializes its gRPC clients. ([#&#8203;14663](https://github.com/open-telemetry/opentelemetry-collector/issues/14663)) When the sending queue and retry are disabled, calling ConsumeTraces, ConsumeMetrics, ConsumeLogs, or ConsumeProfiles before the OTLP exporter initializes its gRPC clients could cause a nil pointer dereference panic. The push methods now return an error instead of panicking. - `exporter/otlp_http`: Show the actual destination URL in error messages when request URL is modified by middleware. ([#&#8203;14673](https://github.com/open-telemetry/opentelemetry-collector/issues/14673)) Unwraps the `*url.Error` returned by `http.Client.Do()` to prevent misleading error logs when a middleware extension dynamically updates the endpoint. - `pdata/pprofile`: Switch the dictionary of dictionary tables entries only once when merging profiles ([#&#8203;14709](https://github.com/open-telemetry/opentelemetry-collector/issues/14709)) For dictionary table data, we used to switch their dictionaries when doing the switch for the data that uses them. However, when an entry is associated with multiple other data (several samples can use the same stack), we would have been switching the dictionaries of the entry multiple times. We now switch dictionaries for dictionary table data only once, before switching the resource profiles. <!-- previous-version --> ### [`v1.53.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1530v01470) ##### 💡 Enhancements 💡 - `exporter/debug`: Output bucket counts for exponential histogram data points in normal verbosity. ([#&#8203;10463](https://github.com/open-telemetry/opentelemetry-collector/issues/10463)) - `pkg/exporterhelper`: Add `metadata_keys` configuration to `sending_queue.batch.partition` to partition batches by client metadata ([#&#8203;14139](https://github.com/open-telemetry/opentelemetry-collector/issues/14139)) The `metadata_keys` configuration option is now available in the `sending_queue.batch.partition` section for all exporters. When specified, batches are partitioned based on the values of the listed metadata keys, allowing separate batching per metadata partition. This feature is automatically configured when using `exporterhelper.WithQueue()`. ##### 🧰 Bug fixes 🧰 - `cmd/builder`: Fix duplicate error output when CLI command execution fails in the builder tool. ([#&#8203;14436](https://github.com/open-telemetry/opentelemetry-collector/issues/14436)) - `cmd/mdatagen`: Fix duplicate error output when CLI command execution fails in the mdatagen tool. ([#&#8203;14436](https://github.com/open-telemetry/opentelemetry-collector/issues/14436)) - `cmd/mdatagen`: Fix semconv URL validation for metrics with underscores in their names ([#&#8203;14583](https://github.com/open-telemetry/opentelemetry-collector/issues/14583)) Metrics like `system.disk.io_time` now correctly validate against semantic convention URLs containing underscores in the anchor tag. - `extension/memory_limiter`: Use ChainUnaryInterceptor instead of UnaryInterceptor to allow multiple interceptors. ([#&#8203;14634](https://github.com/open-telemetry/opentelemetry-collector/issues/14634)) If multiple extensions that use the UnaryInterceptor are set the binary panics at start time. - `extension/memory_limiter`: Add support for streaming services. ([#&#8203;14634](https://github.com/open-telemetry/opentelemetry-collector/issues/14634)) - `pkg/config/configmiddleware`: Add context.Context to HTTP middleware interface constructors. ([#&#8203;14523](https://github.com/open-telemetry/opentelemetry-collector/issues/14523)) This is a breaking API change for components that implement or use extensionmiddleware. - `pkg/confmap`: Fix another issue where configs could fail to decode when using interpolated values in string fields. ([#&#8203;14034](https://github.com/open-telemetry/opentelemetry-collector/issues/14034)) For example, a resource attribute can be set via an environment variable to a string that is parseable as a number, e.g. `1234`. (A similar bug was fixed in a previous release: that one was triggered when the field was nested in a struct, whereas this one is triggered when the field internally has type "pointer to string" rather than "string".) - `pkg/otelcol`: The featuregate subcommand now rejects extra positional arguments instead of silently ignoring them. ([#&#8203;14554](https://github.com/open-telemetry/opentelemetry-collector/issues/14554)) - `pkg/queuebatch`: Fix data race in partition\_batcher where resetTimer() was called outside mutex, causing concurrent timer.Reset() calls and unpredictable batch flush timing under load. ([#&#8203;14491](https://github.com/open-telemetry/opentelemetry-collector/issues/14491)) - `pkg/scraperhelper`: Log scrapers now emit log-appropriate receiver telemetry ([#&#8203;14654](https://github.com/open-telemetry/opentelemetry-collector/issues/14654)) Log scrapers previously emitted the same receiver telemetry as metric scrapers, such as the otelcol\_receiver\_accepted\_metric\_points metric (instead of otelcol\_receiver\_accepted\_log\_records), or spans named receiver/myreceiver/MetricsReceived (instead of receiver/myreceiver/LogsReceived). This did not affect scraper-specific spans and metrics. - `processor/batch`: Fixes a bug where the batch processor would not copy `SchemaUrl` metadata from resource and scope containers during partial batch splits. ([#&#8203;12279](https://github.com/open-telemetry/opentelemetry-collector/issues/12279), [#&#8203;14620](https://github.com/open-telemetry/opentelemetry-collector/issues/14620)) <!-- previous-version --> ### [`v1.52.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1520v01461) <!-- previous-version --> ### [`v1.51.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1510v01450) ##### 💡 Enhancements 💡 - `pkg/scraperhelper`: ScraperID has been added to the logs for metrics, logs, and profiles ([#&#8203;14461](https://github.com/open-telemetry/opentelemetry-collector/issues/14461)) ##### 🧰 Bug fixes 🧰 - `exporter/otlp_grpc`: Fix the OTLP exporter balancer to use round\_robin by default, as intended. ([#&#8203;14090](https://github.com/open-telemetry/opentelemetry-collector/issues/14090)) - `pkg/config/configoptional`: Fix `Unmarshal` methods not being called when config is wrapped inside `Optional` ([#&#8203;14500](https://github.com/open-telemetry/opentelemetry-collector/issues/14500)) This bug notably manifested in the fact that the `sending_queue::batch::sizer` config for exporters stopped defaulting to `sending_queue::sizer`, which sometimes caused the wrong units to be used when configuring `sending_queue::batch::min_size` and `max_size`. As part of the fix, `xconfmap` exposes a new `xconfmap.WithForceUnmarshaler` option, to be used in the `Unmarshal` methods of wrapper types like `configoptional.Optional` to make sure the `Unmarshal` method of the inner type is called. The default behavior remains that calling `conf.Unmarshal` on the `confmap.Conf` passed as argument to an `Unmarshal` method will skip any top-level `Unmarshal` methods to avoid infinite recursion in standard use cases. - `pkg/confmap`: Fix an issue where configs could fail to decode when using interpolated values in string fields. ([#&#8203;14413](https://github.com/open-telemetry/opentelemetry-collector/issues/14413)) For example, a header can be set via an environment variable to a string that is parseable as a number, e.g. `1234` - `pkg/service`: Don't error on startup when process metrics are enabled on unsupported OSes (e.g. AIX) ([#&#8203;14307](https://github.com/open-telemetry/opentelemetry-collector/issues/14307)) <!-- 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-02-15 00:27:01 +01:00
chore(deps): update module go.opentelemetry.io/collector/confmap to v1.51.0
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
CI / test (push) Successful in 2m0s
Details
d90b088949
renovate-bot commented 2026-02-15 00:27:02 +01: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):

  • 1 additional dependency was updated

Details:

Package Change
github.com/knadh/koanf/v2 v2.3.0 -> v2.3.3
### ℹ️ 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): - 1 additional dependency was updated Details: | **Package** | **Change** | | :-------------------------- | :------------------- | | `github.com/knadh/koanf/v2` | `v2.3.0` -> `v2.3.3` |
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/confmap to v1.51.0 to chore(deps): update module go.opentelemetry.io/collector/confmap to v1.52.0 2026-02-25 12:13:45 +01:00
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-confmap-1.x from d90b088949 to 18d88a1645 2026-02-25 12:13:46 +01:00 Compare
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/confmap to v1.52.0 to chore(deps): update module go.opentelemetry.io/collector/confmap to v1.53.0 2026-03-10 12:19:44 +01:00
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-confmap-1.x from 18d88a1645 to a64f31a903 2026-03-10 12:19:44 +01:00 Compare
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-confmap-1.x from a64f31a903 to 4704c4bf7a 2026-03-19 08:15:24 +01:00 Compare
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-confmap-1.x from 4704c4bf7a to e730124ee6 2026-03-19 09:09:03 +01:00 Compare
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-confmap-1.x from e730124ee6 to b7ca6d2393 2026-03-25 12:15:29 +01:00 Compare
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/confmap to v1.53.0 to chore(deps): update module go.opentelemetry.io/collector/confmap to v1.54.0 2026-03-25 12:15:29 +01:00
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-confmap-1.x from b7ca6d2393 to e8ff0f4944 2026-03-26 21:09:47 +01:00 Compare
t.behrendt approved these changes 2026-03-26 21:22:42 +01:00
t.behrendt merged commit 34d4be9a64 into main 2026-03-26 21:22:50 +01:00
t.behrendt deleted branch renovate/go.opentelemetry.io-collector-confmap-1.x 2026-03-26 21:22:50 +01: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#33
Delete Branch "renovate/go.opentelemetry.io-collector-confmap-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?