# OpenTelemetry v0.142.0

2025-12-15 · [Original release notes](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.142.0) · [Full summary](https://ratatosk.io/en/releases/opentelemetry/v0.142.0)

Breaking changes 3 · Deprecations 1 · Important fixes 1 · Enhancements 2 · Other changes 2

## Breaking changes (3)

### Static gRPC endpoint validation extended to all clients

- Affects: gRPC clients using `pkg/config/configgrpc`

Before this change, the validation was performed in the OTLP exporter but was not applied to every gRPC client.

> - `pkg/config/configgrpc`: Statically validate gRPC endpoint (#10451)
>   This validation was already done in the OTLP exporter. It will now be applied to any gRPC client.

### Entity attribute methods renamed

- Affects: the `pdata/xpdata` `Entity` API (Inferred)

`IDAttributes()` is replaced by `IdentifyingAttributes()`, and `DescriptionAttributes()` is replaced by `DescriptiveAttributes()`.

Evidence: “+func (e Entity) IdentifyingAttributes() EntityAttributeMap {” https://github.com/open-telemetry/opentelemetry-collector/pull/14275

> - `pdata/xpdata`: Rename `Entity.IDAttributes()` to `Entity.IdentifyingAttributes()` and `Entity.DescriptionAttributes()` to `Entity.DescriptiveAttributes()` to align with OpenTelemetry specification terminology for attributes. (#14275)

### `pkg/exporterhelper` queue configuration now uses optional types

- Affects: components with `QueueBatchConfig` fields or calls to affected `pkg/exporterhelper` queue helpers (Inferred)

Previously, these fields and helper calls took `exporterhelper.QueueBatchConfig` directly; the optional form preserves the `enabled` subfield. `configoptional.Some(exporterhelper.NewDefaultQueueConfig())` enables by default, while `configoptional.Default(exporterhelper.NewDefaultQueueConfig())` disables by default.

> - `pkg/exporterhelper`: Use `configoptional.Optional` for the `exporterhelper.QueueBatchConfig` (#14155)
>   It's recommended to change the field type in your component configuration to be `configoptional.Optional[exporterhelper.QueueBatchConfig]` to keep the `enabled` subfield. Use configoptional.Some(exporterhelper.NewDefaultQueueConfig()) to enable by default. Use configoptional.Default(exporterhelper.NewDefaultQueueConfig()) to disable by default.

## Deprecations (1)

### Logging options deprecated and zap logger builder added

- Affects: `pkg/service` logging using `Settings.LoggingOptions` or `telemetry.LoggerSettings.ZapOptions`, and `otelcol` setups with zap config that specifies no file output
- Removed in: not stated

`BuildZapLogger` can access `zap.Config`; `otelcol` uses it to install a Windows Event Log output when the zap config specifies no file output.

> - `pkg/service`: Deprecate Settings.LoggingOptions and telemetry.LoggerSettings.ZapOptions, add telemetry.LoggerSettings.BuildZapLogger (#14002)
>   BuildZapLogger provides a more flexible way to build the Zap logger,
>   since the function will have access to the zap.Config. This is used
>   in otelcol to install a Windows Event Log output when the zap config
>   does not specify any file output.

## Important fixes (1)

### Embedded-struct unmarshaling in `pkg/confmap` now preserves `Unmarshal` state

- Affects: embedded structs implementing `Unmarshal`

When an embedded struct implementing `Unmarshal` contained a `configopaque.String`, the hook could send marshaled data through `mapstructure`; because marshaling produced `[REDACTED]`, the value did not round-trip and fields set by `Unmarshal` could be overwritten. The hook now gives `mapstructure` an already-unmarshaled struct and decodes non-`Unmarshaler` subfields separately.

> - `pkg/confmap`: Ensure that embedded structs are not overwritten after Unmarshal is called (#14213)
>   This allows embedding structs which implement Unmarshal and contain a configopaque.String.

## Enhancements (2)

- Optional resource attributes in `pkg/service` internal logs
- `ProfileCount()` added to `pdata/pprofile`

## Other changes (2)

- Dropped-item counts in detailed `exporter/debug` output
- `memorylimiter` available as HTTP/GRPC middleware

---

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