# OpenTelemetry v0.144.0

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

Breaking changes 5 · Deprecations 4 · Enhancements 8 · Other changes 5

## Check before upgrading

### Defects found after release

- Duplicate entries in `otelcol components` fixed · Fixed in v0.146.0
- gRPC client endpoints accept resolver-scheme URIs · Fixed in v0.151.0

## Breaking changes (5)

### Exporter queue batch send-size metric limited to detailed verbosity

- Affects: Collector setups that emit `otelcol_exporter_queue_batch_send_size` (Inferred)

The histogram produces one bucket metric per boundary, which can result in high cardinality.

Evidence: “I think it makes sense to expose the `otelcol_exporter_queue_batch_send_size` metric when telemetry verbosity is set to `detailed` level, consistent with the existing `otelcol_exporter_queue_batch_send_size_bytes` metric.” https://github.com/open-telemetry/opentelemetry-collector/issues/14278

> - `pkg/exporterhelper`: Change verbosity level for otelcol_exporter_queue_batch_send_size metric to detailed. (#14278)

### `telemetry.disableHighCardinalityMetrics` gate removed from `pkg/service`

- Affects: configurations using `telemetry.disableHighCardinalityMetrics` in `pkg/service` (Inferred)

Before removal, the gate controlled whether the collector enabled potentially high-cardinality metrics. The source points to configuring `service::telemetry::metrics::views` instead, but does not state what happens to the prior gate setting after upgrade.

Evidence: “This feature gate has been deprecated since 0.132.0, which is way more than the 2 releases we require for deprecated feature flags.” https://github.com/open-telemetry/opentelemetry-collector/pull/14373

> - `pkg/service`: Remove deprecated `telemetry.disableHighCardinalityMetrics` feature gate. (#14373)

### `service.noopTracerProvider` feature gate removed

- Affects: setups enabling `service.noopTracerProvider`

When enabled, the gate selected a Noop OpenTelemetry TracerProvider to reduce memory allocations; it was incompatible with the zPages extension.

Evidence: “This feature gate has been deprecated since 0.132.0, which is way more than the 2 releases we require for deprecated feature flags.” https://github.com/open-telemetry/opentelemetry-collector/pull/14374

> - `pkg/service`: Remove deprecated `service.noopTracerProvider` feature gate. (#14374)

### `confighttp` replaces its HTTP server endpoint field

- Affects: HTTP server configurations using `pkg/config/confighttp` (Inferred)

The former `ServerConfig.Endpoint` field is replaced by `NetAddr confignet.AddrConfig`, and a `transport` option allows protocols such as `tcp` and `unix`.

> - `pkg/config/confighttp`: Replace `ServerConfig.Endpoint` with `NetAddr confignet.AddrConfig`, enabling more flexible transport configuration. (#14187, #8752)
>   This change adds "transport" as a configuration option, allowing users to specify
>   different transport protocols (e.g., "tcp", "unix").

### `pkg/xconnector` Create methods validate component ID types

- Affects: setups using `pkg/xconnector` factory `Create` methods (Inferred)

Matching ID types proceed to the corresponding create function; mismatched types return an ID-mismatch error.

Evidence: “Adds component ID type validation to all xconnector Create methods to match the pattern used in the all other factories. The checks were missed in https://github.com/open-telemetry/opentelemetry-collector/pull/12381” https://github.com/open-telemetry/opentelemetry-collector/pull/14357

> - `pkg/xconnector`: Add component ID type validation to all xconnector Create methods (#14357)

## Deprecations (4)

### OTLP exporter type renamed to `otlp_grpc`

- Affects: Configurations using the `otlp` or `otlp_grpc` exporter type (Inferred)
- Removed in: not stated

Configurations using `otlp` continue to work through a deprecated alias.

> - `exporter/otlp_grpc`: Rename `otlp` exporter to `otlp_grpc` exporter and add deprecated alias `otlp`. (#14403)

### Exporter renamed to `otlp_http`, with `otlphttp` retained as a deprecated alias

- Affects: setups configured with the `otlphttp` exporter
- Removed in: not stated

Configurations using `otlphttp` continue to use the original implementation and automatically log a deprecation warning.

> - `exporter/otlp_http`: Rename `otlphttp` exporter to `otlp_http` exporter and add deprecated alias `otlphttp`. (#14396)

### `pkg/scraperhelper` deprecates `AddScraper` in favor of `AddMetricsScraper`

- Affects: `pkg/scraperhelper` code using `AddScraper` (Inferred)
- Removed in: not stated

Existing callers continue to work because `AddScraper` delegates to `AddMetricsScraper`.

> - `pkg/scraperhelper`: Deprecate the `AddScraper` method. (#14428)
> - `pkg/scraperhelper`: Introduce `AddMetricsScraper` to be more explicit than `AddScraper`. (#14428)

### Deprecated type alias registration in `xextension`

- Affects: extension configurations using a registered deprecated type alias
- Removed in: not stated

When configuration uses a registered alias, a deprecation warning is logged automatically, and the extension functions using it run the original implementation.

> - `extension/xextension`: Add deprecated type alias support for extensions via `xextension` module (#14208)
>   Extensions can now register deprecated type aliases using the experimental `xextension.WithDeprecatedTypeAlias` option.
>   ```go
>   return xextension.NewFactory(
>       metadata.Type,
>       createDefaultConfig,
>       createExtension,
>       metadata.Stability,
>       xextension.WithDeprecatedTypeAlias("old_extension_name"),
>   )
>   ```
>   When the alias is used in configuration, a deprecation warning will be automatically logged, and the extension will function normally using the original implementation.
> - `all`: Add support for deprecated component type aliases (#14208)
>   To add a deprecated type alias to a component factory, use the `WithDeprecatedTypeAlias` option.
>   ```go
>   return xexporter.NewFactory(
>       metadata.Type,
>       createDefaultConfig,
>       xexporter.WithTraces(createTracesExporter, metadata.TracesStability),
>       xexporter.WithDeprecatedTypeAlias("old_component_name"),
>   )
>   ```
>   When the alias is used in configuration, a deprecation warning will be automatically logged, and the component will function normally using the original implementation.

## Enhancements (8)

- Profiles support added to `receiver/nop`
- Added `pkg/xscraperhelper` for OTel Profiling receivers (To use: `pkg/xscraperhelper` must be used along with `scraper/xscraper` to enable OTel Profiling signal receivers.)
- Metric-level attribute disabling and data-point re-aggregation in `cmd/mdatagen`
- Profile count method for the consumertest profiles sink
- Profile-sample counters for `exporterhelper` exporters
- Profile-sample operation reporting in `receiverhelper.ObsReport`
- Explicit `AddMetricsScraper` helper for metrics scraper configuration
- OTLP receiver adds profile-sample metrics

## Other changes (5)

- Duplicate CLI error logging fixed in builder-generated collector binaries
- Optional `display_name` and `description` fields in `metadata.yaml`
- Entity stability value validation in `cmd/mdatagen`
- Profile batching re-enabled in `pkg/xexporterhelper`
- Partition batcher reference-count bug fixed

---

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