Note: I'm not sure if this change can be reflected in schema-next.yaml 🤔 .

It can, you can list the metrics that are affected and the attribute change. See for example: https://github.com/open-telemetry/semantic-conventions/blob/main/schemas/1.28.0#L48

Thank's @joaopgrassi . My concern here is that system.device is not entirely removed, it's still used as an attribute in other metrics. Here we just replace its usage in specific metrics. I guess this can be reflected in the schema-next as you mentioned, but should this also be added in the deprecated file(s)?

but should this also be added in the deprecated file(s)?

I believe yes, each "area" now has its own deprecated file, so within that usage, the attribute is considered deprecated. There then it's also mentioned which one to use instead.

@lmolkova @jsuereth is this correct in your view? Not sure if we had such case before 🤔

but should this also be added in the deprecated file(s)?

I believe yes, each "area" now has its own deprecated file, so within that usage, the attribute is considered deprecated. There then it's also mentioned which one to use instead.

@lmolkova @jsuereth is this correct in your view? Not sure if we had such case before 🤔

Appears that we can't model this right now?

I get:

> make fix

Diagnostic report:

  × The attribute id `system.device` is declared multiple times in the
  │ following groups:
  │ ["registry.container.metrics.deprecated",
  │ "registry.system.metrics.deprecated", "registry.system"]

/cc @joaopgrassi

Appears that we can't model this right now?

There is no need to deprecate attributes if it's still used.

The only thing you need to do is to write the proper section in the schema-next (which you already did!)

@open-telemetry/semconv-system-approvers could you review this one please ?