Define semantic conventions for k8s metrics #1032
Comments
ChrsMark
added
enhancement
|
I love the idea of moving forward with this work. According to the collector end-user survey k8s and the collector are a big part of our end-user's stack, so moving the related semconvs forwards is a great idea. |
|
In general, my team has been happy with the metrics collected by |
#33598) Having recently been working with the `kubeletstats` receiver (using it and contributing to it), I would like to volunteer to help with its maintainance by intending to dedicate time to contribute to the component as well as help with the existing and future issue queue. Also being a member of the [semconv-k8s-approvers](https://github.com/orgs/open-telemetry/teams/semconv-k8s-approvers) and [semconv-container-approvers](https://github.com/orgs/open-telemetry/teams/semconv-container-approvers) will help to bring more alignment between the [Semantic Conventions](open-telemetry/semantic-conventions#1032) and the Collector's implementation within this specific scope. - ✅ Being a member of Opentelemetry organization - PRs authored: https://github.com/open-telemetry/opentelemetry-collector-contrib/pulls?q=is%3Apr+author%3AChrsMark++label%3Areceiver%2Fkubeletstats%2Cinternal%2Fkubeletstats%2Cinternal%2Fkubelet - Issues have been involved: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aissue+commenter%3AChrsMark+label%3Areceiver%2Fkubeletstats%2Cinternal%2Fkubeletstats+ /cc @dmitryax @TylerHelmuth with whom I have already discussed about it Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
open-telemetry#33598) Having recently been working with the `kubeletstats` receiver (using it and contributing to it), I would like to volunteer to help with its maintainance by intending to dedicate time to contribute to the component as well as help with the existing and future issue queue. Also being a member of the [semconv-k8s-approvers](https://github.com/orgs/open-telemetry/teams/semconv-k8s-approvers) and [semconv-container-approvers](https://github.com/orgs/open-telemetry/teams/semconv-container-approvers) will help to bring more alignment between the [Semantic Conventions](open-telemetry/semantic-conventions#1032) and the Collector's implementation within this specific scope. - ✅ Being a member of Opentelemetry organization - PRs authored: https://github.com/open-telemetry/opentelemetry-collector-contrib/pulls?q=is%3Apr+author%3AChrsMark++label%3Areceiver%2Fkubeletstats%2Cinternal%2Fkubeletstats%2Cinternal%2Fkubelet - Issues have been involved: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aissue+commenter%3AChrsMark+label%3Areceiver%2Fkubeletstats%2Cinternal%2Fkubeletstats+ /cc @dmitryax @TylerHelmuth with whom I have already discussed about it Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
|
I have updated the description to group metrics together in a meaningful way. I hope this makes the list less overwhelming and people willing to help on this could pick up a group all together and work on it. Maybe we could create standalone issues per group if that helps, link them here to simplify the list in this issue's description and use this issue as a meta issue. |
Area(s)
area:k8s
Is your change request related to a problem? Please describe.
At the moment there are not Semantic Conventions for k8s metrics.
Describe the solution you'd like
Even if we cannot consider the k8s metrics as stable we can start considering adding metrics that are not controversial to get some progress here. This issue aims to collect the existing k8s metrics that exist in the Collector and keep track of any related work.
Bellow I'm providing an initial list with metrics coming from the
kubeletstatsandk8sclusterreceivers. Note that these are matter to change with time being so we should get back to the Collector to verify the current state.cc: @open-telemetry/semconv-k8s-approvers
Describe alternatives you've considered
No response
Additional context
Below there are some metrics from namespaces other than
k8s.*as well. I leave them in there intentionally in order to take them into account accordingly.kubeletstats metrics
cpu metrics
k8s.node.cpu.usagek8s.node.cpu.utilizationk8s.node.cpu.timek8s.pod.cpu.usagek8s.pod.cpu.utilization:Deprecatedk8s.pod.cpu.timek8s.pod.cpu.node.utilizationk8s.pod.cpu_limit_utilizationk8s.pod.cpu_request_utilizationcontainer.cpu.usage: #1128container.cpu.utilization:Deprecatedcontainer.cpu.time✅ #282k8s.container.cpu_limit_utilizationk8s.container.cpu_request_utilizationk8s.container.cpu.node.utilizationk8s.container.memory.node.utilizationmemory metrics
k8s.node.memory.availablek8s.node.memory.usagek8s.node.memory.rssk8s.node.memory.working_setk8s.node.memory.page_faultsk8s.node.memory.major_page_faultsk8s.pod.memory.availablek8s.pod.memory.usagek8s.pod.memory.node.utilizationk8s.pod.memory_limit_utilizationk8s.pod.memory_request_utilizationk8s.pod.memory.rssk8s.pod.memory.working_setk8s.pod.memory.page_faultsk8s.pod.memory.major_page_faultscontainer.memory.availablecontainer.memory.usage: ✅ #282k8s.container.memory_limit_utilizationk8s.container.memory_request_utilizationcontainer.memory.rsscontainer.memory.working_setcontainer.memory.page_faultscontainer.memory.major_page_faultsfilesystem metrics
k8s.node.filesystem.availablek8s.node.filesystem.capacityk8s.node.filesystem.usagek8s.pod.filesystem.availablek8s.pod.filesystem.capacityk8s.pod.filesystem.usagecontainer.filesystem.availablecontainer.filesystem.capacitycontainer.filesystem.usagenetwork metrics
k8s.node.network.iok8s.node.network.errorsk8s.pod.network.iok8s.pod.network.errorsuptime metrics
k8s.node.uptimek8s.pod.uptimecontainer.uptimevolume metrics
k8s.volume.availablek8s.volume.capacityk8s.volume.inodesk8s.volume.inodes.freek8s.volume.inodes.usedk8scluster metrics
container metrics
k8s.container.cpu_requestk8s.container.cpu_limitk8s.container.memory_requestk8s.container.memory_limitk8s.container.storage_requestk8s.container.storage_limitk8s.container.ephemeralstorage_requestk8s.container.ephemeralstorage_limitk8s.container.restartsk8s.container.readypod metrics
k8s.pod.phasek8s.pod.status_reasondeployment metrics
k8s.deployment.desiredk8s.deployment.availablecronjob metrics
k8s.cronjob.active_jobsdaemonset metrics
k8s.daemonset.current_scheduled_nodesk8s.daemonset.desired_scheduled_nodesk8s.daemonset.misscheduled_nodesk8s.daemonset.ready_nodeshpa metrics
k8s.hpa.max_replicask8s.hpa.min_replicask8s.hpa.current_replicask8s.hpa.desired_replicasjob metrics
k8s.job.active_podsk8s.job.desired_successful_podsk8s.job.failed_podsk8s.job.max_parallel_podsk8s.job.successful_podsnamespace metrics
k8s.namespace.phasereplicaset metrics
k8s.replicaset.desiredk8s.replicaset.availablereplication_controller metrics
k8s.replication_controller.desiredk8s.replication_controller.availableresource_quota metrics
k8s.resource_quota.hard_limitk8s.resource_quota.usedstatefulset metrics
k8s.statefulset.desired_podsk8s.statefulset.ready_podsk8s.statefulset.current_podsk8s.statefulset.updated_podsOpenshift metrics
openshift.clusterquota.limitopenshift.clusterquota.usedopenshift.appliedclusterquota.limitopenshift.appliedclusterquota.usednode metrics
k8s.node.conditionRelated issues
TBA
The text was updated successfully, but these errors were encountered: