# OpenTelemetry v0.147.0

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

Breaking changes 4 · Important fixes 3 · Enhancements 2 · Other changes 5

## Breaking changes (4)

### Log scrapers emit log-appropriate receiver telemetry

- Affects: Setups that use log scrapers in `pkg/scraperhelper` (Inferred)

Previously, log scrapers emitted `otelcol_receiver_accepted_metric_points` and `receiver/myreceiver/MetricsReceived` instead of `otelcol_receiver_accepted_log_records` and `receiver/myreceiver/LogsReceived`. Scraper-specific spans and metrics are unaffected.

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

### Streaming support added to the `memory_limiter` extension

- Affects: setups using the `memory_limiter` extension with gRPC streaming services (Inferred)

Streaming requests receive `RESOURCE_EXHAUSTED` when `MustRefuse()` is true.

> - `extension/memory_limiter`: Add support for streaming services. (#14634)

### `featuregate` rejects extra positional arguments

- Affects: the `featuregate` subcommand (Inferred)

Previously, invocations with more than one positional argument succeeded and silently ignored the extras; they now return an error.

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

### gRPC middleware constructors now accept `context.Context`

- Affects: gRPC middleware implementations and constructors in `pkg/config/configmiddleware` or `pkg/extensionmiddleware`

Option functions can retrieve options through a remote call, such as reading TLS configuration from a sidecar.

Evidence: “Interfaces like GRPCClient/GRPCServer for the option function should accept context as first param. This is important if to retrieve some option a remote call is needed, for example read TLS config from a sidecar.” https://github.com/open-telemetry/opentelemetry-collector/issues/14523

> - `pkg/config/configmiddleware`: Add context.Context to gRPC middleware interface constructors. (#14523)
> - `pkg/extensionmiddleware`: Add context.Context to gRPC middleware interface constructors. (#14523)
>   This is a breaking API change for components that implement or use extensionmiddleware.
> - `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.

## Important fixes (3)

### `processor/batch` SchemaUrl copying fixed

- Affects: setups using `processor/batch` (Inferred)

During partial batch splits, `processor/batch` did not copy `SchemaUrl` metadata from resource and scope containers. It now copies that metadata during partial batch splits.

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

### Memory limiter chains unary interceptors

- Affects: setups using the memory_limiter extension with multiple extensions that use `UnaryInterceptor` (Inferred)

When multiple extensions using `UnaryInterceptor` were configured, gRPC's single-interceptor limit caused the binary to panic at startup; the memory_limiter extension now chains their unary interceptors.

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

### Config decoding fixed for interpolated pointer-to-string fields

- Affects: configurations with interpolated values in fields internally typed as pointer to string

Before this fix, an interpolated environment-variable value such as `1234` was treated as an integer and failed string validation, so configuration decoding failed.

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

## Enhancements (2)

- Metadata-based exporter batch partitioning (To use: Specify `metadata_keys` in `sending_queue.batch.partition`; `exporterhelper.WithQueue()` configures the partitioner and merge function automatically.)
- Semantic-convention URLs with underscore anchors validated by `cmd/mdatagen`

## Other changes (5)

- `exporter/debug` outputs exponential histogram bucket counts
- Duplicate `cmd/builder` CLI error output fixed
- Duplicate CLI error output fixed in `cmd/mdatagen`
- Race in `partition_batcher` timer reset fixed
- `pkg/xexporterhelper` adds handling for unbounded sending-queue partitions

---

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