# OpenTelemetry v0.145.0

2026-02-02 · [Original release notes](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0) · [Full summary](https://ratatosk.io/en/releases/opentelemetry/v0.145.0)

Important fixes 5 · Enhancements 2 · Other changes 2

## Important fixes (5)

### OTLP gRPC exporter default balancer fixed to `round_robin`

- Affects: setups using the `exporter/otlp_grpc` OTLP exporter with its default balancer (Inferred)

With the default balancer, behavior could fall back to `pick_first`; with the passthrough resolver scheme, `round_robin` did not take effect.

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

### Exporter batch sizer defaults restored

- Affects: exporter configurations using `sending_queue` batching (Inferred)

When configuration was wrapped in `Optional`, its `Unmarshal` method could be skipped, leaving batch `min_size` and `max_size` in the wrong units. Wrapper types can now use `xconfmap.WithForceUnmarshaler` to call the inner `Unmarshal`; top-level `Unmarshal` calls on `confmap.Conf` still skip top-level methods by default.

> - `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
>   As part of the fix, `xconfmap` exposes a new `xconfmap.WithForceUnmarshaler` option, to be used in the `Unmarshal` methods
>   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/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`.

### Optional-wrapped config unmarshalling and exporter batch sizer default fixed

- Affects: exporter configuration wrapped in `Optional`, especially configurations using `sending_queue::batch::sizer`, `sending_queue::batch::min_size` or `sending_queue::batch::max_size`

The `sending_queue::batch::sizer` setting could stop defaulting to `sending_queue::sizer`, causing `sending_queue::batch::min_size` and `max_size` to use the wrong units. That default is restored.

> - `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`.

### Interpolated string decoding fixed in `pkg/confmap` struct collections

- Affects: configurations with interpolated values in string fields within collections of structs

Before the fix, a value that parsed as a non-string, such as an environment-supplied `1234`, could make decoding fail. With `confmap.newExpandedValueSanitizer` enabled, per-field decoding avoids that failure.

> - `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`

### Unsupported-OS process-metrics startup error fixed in `pkg/service`

- Affects: custom-compiled collectors on unsupported operating systems with process metrics enabled

These collectors previously failed to start with `failed to register process metrics: not implemented yet`; they now start without that error.

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

## Enhancements (2)

- Forced inner unmarshaling for wrapper types (To use: Wrapper types' `Unmarshal` methods must use `xconfmap.WithForceUnmarshaler` to ensure the inner type's `Unmarshal` method is called.)
- `AddProfilesScraper` helper added to `pkg/xscraperhelper`

## Other changes (2)

- Scraper IDs added to `pkg/scraperhelper` error logs
- `pkg/config/configgrpc` adds client info before server authentication

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
