Area(s)
area:container
area:system
area:process
Is your change request related to a problem? Please describe.
At the moment we have 3 different metric attributes representing the cpu.state:
Based on the global flat registry idea it would be nice if we had one single definition for this attribute and then be able to re-use it in the various namespaces.
Describe the solution you'd like
As it is explained at #681 (comment) we could consider merging into one single one called cpu.state similar to the disk.io.direction and network.io.direction.
Describe alternatives you've considered
Maybe the embed concept would be sth to think of here: open-telemetry/build-tools#240
Additional context
No response
cc @open-telemetry/semconv-system-approvers @open-telemetry/semconv-container-approvers @open-telemetry/semconv-k8s-approvers
Area(s)
area:container
area:system
area:process
Is your change request related to a problem? Please describe.
At the moment we have 3 different metric attributes representing the
cpu.state:system.cpu.stateprocess.cpu.statecontainer.cpu.stateBased on the global flat registry idea it would be nice if we had one single definition for this attribute and then be able to re-use it in the various namespaces.
Describe the solution you'd like
As it is explained at #681 (comment) we could consider merging into one single one called
cpu.statesimilar to thedisk.io.directionandnetwork.io.direction.Describe alternatives you've considered
Maybe the
embedconcept would be sth to think of here: open-telemetry/build-tools#240Additional context
No response
cc @open-telemetry/semconv-system-approvers @open-telemetry/semconv-container-approvers @open-telemetry/semconv-k8s-approvers