-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[receiver/kubeletstats] Can we have CSI information as Resource Attributes of k8s.volume.* metrics? #27580
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Sounds like a reasonable addition as optional attributes. @haihh05 do you want to contribute and add them? |
Thanks, @dmitryax. I will think about it. But now I have no idea where I need to start from. |
I think this would be a useful addition. Fwiw, the 3 k8s in-tree volume sources, |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/kubeletstats
Is your feature request related to a problem? Please describe.
I would like to use OTEL with receiver/kubeletstats instead of kube-state-metrics for K8s monitoring, but I need some csi information.
In my current K8s, I had ceph cluster for k8s storage, then I can map csi_volume_handle to the image in ceph to get I/O metrics of each pv on k8s.
I believe that we will need that if we use the external storage.
Describe the solution you'd like
It is nice to have csi_volume_handle and csi_drive labels (like kube_persistentvolume_info metric in kube-state-metrics)
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: