Telemetry metric metadata uses deprecated field not supported by mdatagen

[Syedowais312]

Component(s)

No response

Is your feature request related to a problem? Please describe.

After opentelemetry-collector PR , mdatagen now open-telemetry/opentelemetry-collector#14408 enforces the
metadata schema and no longer allows deprecated under telemetry.metrics.

Several contrib components (e.g. kafkareceiver) still define telemetry
metrics using:

telemetry.metrics..deprecated

These must be migrated to:

telemetry.metrics..stability: deprecated

This issue tracks updating contrib metadata to be compatible with the
updated schema.

Describe the solution you'd like

Describe the solution you'd like

Update contrib component metadata to comply with the current mdatagen schema by removing the unsupported deprecated field under telemetry.metrics.

For telemetry metrics that are deprecated, the metadata should instead use:

stability: deprecated

This change will make contrib metadata compatible with the updated mdatagen validation introduced in opentelemetry-collector and restore successful go generate and CI runs.

This issue will be addressed once the collector PR is merged.

Describe alternatives you've considered

No response

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[ChrsMark]

Just for reference. The change affects not only internal telemetry but receiver's metrics too.

i.e.: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/apachereceiver/metadata.yaml#L72-L73

We should tune the whole Contrib accordingly once open-telemetry/opentelemetry-collector#14113 is completed.

[Syedowais312]

I strongly with this. Once the changes in open-telemetry/opentelemetry-collector#14113 are merged. We can proceed with addressing this issue.

One additional thought: do you think it would make sense to open a corresponding issue in opentelemetry-collector as well, since the schema change originates there and affects both internal and receiver metrics? That could help with visibility and coordination across repos

[ChrsMark]

Yeap, opentelemetry-collector will need to be updated too. I'd expect that it can happen maybe in the same PR that introduce the breaking change in mdatagen.

[Syedowais312]

Hey @ChrsMark, that makes sense 👍

One small thought: would it be useful to create a separate issue just to track the receiver-side metadata changes, mainly for visibility and review clarity?

Even if the actual update still happens in the same PR as the mdatagen breaking change, having a focused issue could help ensure the receiver impact is clearly tracked.

Curious what you think.