The gap between volume used space of metrics | NetApp | Page 1

faint eagle Jan 9, 2024, 8:37 AM

#

pod-0 k8s 85.9G => from the Pod, shows the space of PVC.
kube metrics 96.78G => from the kube Metrics
Netap metrics 79.34G => from NetApp Metrics "volume_size_used", which has the same value shows in AIQUM

[ kube Metrics calculation query ]
kubelet_volume_stats_used_bytes{namespace=~"tspmon.", persistentvolumeclaim=~"prometheus."} /1024/1024/1024

[ NetApp Metrics calculation query ]
max by (volume_name)(volume_size_used{volume_name=~'(pvc-1e478fca-176a-49b1-a016-20e25ea92700|pvc-84485bab-efe0-4890-adbb-3feff4db46bd)'}) /1024/1024/1024

There are a gap between these three numbers: 85.9G, 96.78G, 79.34G, what could be the reason resulting the gap.

Is the "volume_size_used" querying the same data source as "volume_space_physical_used"?

rugged lion Jan 9, 2024, 9:04 AM

#

@faint eagle You can find relevant mapping here
https://netapp.github.io/harvest/latest/ontap-metrics/#volume_space_physical_used
https://netapp.github.io/harvest/latest/ontap-metrics/#volume_size_used

faint eagle Jan 9, 2024, 9:09 AM

#

Thanks @rugged lion Since I found that both metric return the same value.
Also, any idea about the gap?

#The gap between volume used space of metrics