[k8s] Define semantic conventions for k8s cpu metrics #1489
Labels
area:k8s
enhancement
New feature or request
experts needed
This issue or pull request is outside an area where general approvers feel they can approve
triage:needs-triage
Area(s)
area:k8s
Is your change request related to a problem? Please describe.
As part of the K8s SemConv stability work we need to define k8s cpu metrics that are already in use by the Opentelemetry Collector.
Related to #1032
Describe the solution you'd like
The existing metrics in use that we need to define as semantic conventions are the following:
k8s.node.cpu.usage
:✅ #1320k8s.node.cpu.utilization
: Blocked until open-telemetry/opentelemetry-collector-contrib#27885 (comment) is coveredk8s.node.cpu.time
: ✅ #1320k8s.pod.cpu.usage
: ✅ #1320k8s.pod.cpu.utilization
:Deprecated
k8s.pod.cpu.time
: ✅ #1320container.cpu.usage
: ✅ #1128container.cpu.utilization
:Deprecated
container.cpu.time
✅ #282k8s.container.cpu_limit_utilization
k8s.container.cpu_request_utilization
k8s.container.cpu.node.utilization
k8s.pod.cpu.node.utilization
k8s.pod.cpu_limit_utilization
k8s.pod.cpu_request_utilization
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: