# OpenTelemetry v0.146.0

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

Security 1 · Breaking changes 3 · Deprecations 1 · Important fixes 3 · Enhancements 7 · Other changes 3

## Check before upgrading

### Known issues

- **Builder `telemetry` field is for custom SDKs**
  >   intend to provide your own OpenTelemetry SDK.

## Security (1)

### Confighttp bounds request-method cardinality in server span names

- Affects: server internal telemetry from `pkg/config/confighttp`

Previously, raw methods such as `FOOBAR` could appear in span names, producing high cardinality.

> - `pkg/config/confighttp`: Fix high cardinality span name from request method from confighttp server internal telemetry (#14516)
>   Follow spec to bound request method cardinality.

## Breaking changes (3)

### Minimum Go version for builds raised to 1.25

- Affects: Collector builds using Go earlier than 1.25 (Inferred)
- Action required: Go 1.25 or later must be available to build the project.

Previously, the project used Go 1.24.* with a module Go version of 1.24.0.

> - `all`: Increase minimum Go version to 1.25 (#14567)

### Metric stability field flattened in `cmd/mdatagen`

- Affects: metric metadata in `metadata.yaml` processed by `cmd/mdatagen` (Inferred)

Previously, `stability` was a group containing `level` and could contain `since` when the level was `deprecated`. Deprecation is now represented in a separate `deprecated` group, where additional deprecation data is set.

Evidence: “Currently, we define `stability` as a group that typically includes only the `level` field. The only additional field used is `since`, which applies to the `deprecated` stability level.” https://github.com/open-telemetry/opentelemetry-collector/issues/14113

> - `cmd/mdatagen`: Flatten the metric stability field (#14113)
>   So we better match the weaver schema. Additional deprecation data can be set within the `deprecated` field.

### Entity-association requirement for `cmd/mdatagen` metrics and events

- Affects: `cmd/mdatagen` metadata defining entities alongside metrics or events

The generated config can disable individual resource attributes without considering their entity associations, which can disable an identifying entity attribute and produce invalid entity data. When entities are defined, metadata for metrics and events must meet the entity-association requirement.

> - `cmd/mdatagen`: Add entity association requirement for metrics and events when entities are defined (#14284)

## Deprecations (1)

### `pprofile` aggregation API deprecated

- Affects: code using `pdata/pprofile` aggregation elements (Inferred)
- Removed in: not stated

`AggregationTemporality`, its constants, and its `String` method are marked deprecated; the Profiles signal has no replacement for them.

> - `pdata/pprofile`: Declare removed aggregation elements as deprecated. (#14528)
> - `pdata/pprofile`: Declare removed aggregation elements as deprecated. (#14528)

## Important fixes (3)

### Duplicate entries in `otelcol components` fixed

- Affects: generated collectors with component aliases (Inferred)

In v0.144.0, running `otelcol components` in a generated collector could list OTLP exporters such as `otlp_grpc` and `otlp_http` twice.

> - `pkg/otelcol`: Ignore component aliases in the `otelcol components` command (#14492)

### Generated metrics reset `aggDataPoints` during initialization

- Affects: generated metrics using reaggregation

With reaggregation enabled, after enough emit cycles, `emit()` could read counters that no longer matched the datapoints slice and panic with an index-out-of-range error. Resetting `aggDataPoints` in `init()` prevents this mismatch.

> - `cmd/mdatagen`: Reset aggDataPoints during metric init to avoid index out of range panic across emit cycles when reaggregation is enabled. (#14569)

### No-argument panic fixed in `mdatagen`

- Affects: setups that invoke `mdatagen`

Running `mdatagen` without arguments previously caused an index-out-of-range panic; it now returns an argument error.

> - `cmd/mdatagen`: Fix panic when mdatagen is run without arguments. (#14506)

## Enhancements (7)

- Exporter send-failed metrics gain failure attributes (To use: Telemetry level set to Detailed.)
- Experimental `ocb init` subcommand for `cmd/builder`
- Telemetry provider module selection in `cmd/builder` (To use: A `gomod` entry in the telemetry module)
- Deprecated-metric metadata in `cmd/mdatagen` now includes deprecation version and reason
- Optional `relationships` field added to the `cmd/mdatagen` entity schema
- Configurable debug exporter output destinations (To use: `use_internal_logger` must be set to `false` to use `output_paths`)
- Experimental `ToStringMapRaw` function for `confmap.Conf` decoding

## Other changes (3)

- `pdata/pprofile` rejects indexes at the string-table boundary
- Alphabetical ordering for `components` output
- Process signals gated behind build tags in `pkg/otelcol`

---

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