# OpenTelemetry v0.149.0

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

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

## Breaking changes (1)

### `pkg/service` removes service identity labels from internal metrics

- Affects: internal collector metrics

Previously, every internal metric series carried `service_name`, `service_instance_id`, and `service_version` labels. They now appear only in `target_info`, so queries filtering or grouping individual metrics by these labels need `target_info` joins.

> - `pkg/service`: Remove `service_name`, `service_instance_id`, and `service_version` as constant labels on every internal metric datapoint. These attributes are already present in `target_info` and were being duplicated on each series for OpenCensus backwards compatibility. (#14811)
>   Previously, the collector stamped every internal metric series (e.g. `otelcol_process_runtime_heap_alloc_bytes`)
>   with `service_name`, `service_instance_id`, and `service_version` labels to match the old OpenCensus behavior.
>   These attributes are now only present in the `target_info` metric, which is the correct Prometheus/OTel convention.
>   Users who filter or group by these labels on individual metrics will need to update their queries to use
>   `target_info` joins instead.

## Important fixes (2)

### Entity code generation now places `extra_attributes` on the resource

- Affects: entity code generated with `cmd/mdatagen` using `extra_attributes` in entity metadata (Inferred)

When `cmd/mdatagen` generated entity code, attributes such as `k8s.namespace.name` and `k8s.node.name` were added as entity descriptive attributes rather than to the resource.

> - `cmd/mdatagen`: Fix entity code generation so `extra_attributes` are emitted as resource attributes instead of entity descriptive attributes. (#14778)

### `cmd/mdatagen` uses the Go module root for `RootPackage`

- Affects: setups running `cmd/mdatagen` where the Go module root differs from the Git repository root

Since v0.148.0, `cmd/mdatagen` resolved the import root using `helpers.RootPackage`, and running it in this setup could be affected by the mismatch.

> ### 🧰 Bug fixes 🧰
> - `cmd/mdatagen`: Fix RootPackage to use go module root instead of git repo root (#14801)
>   Fixes issue with running mdatagen when the git repository root is different from the go module root.

## Enhancements (2)

- SemConv attribute references in `cmd/mdatagen`
- Generated required-fields validation for mdatagen config Go structs

## Other changes (2)

- aix/ppc64 moved to tier 3 support
- Profiles stability upgraded to alpha

---

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