quota_disk_used is correct - when using the REST collector, the Quota template will gather and export the quota_disk_used metric. When using the ZAPI collector, there is no Quota template, only a Qtree template, which collects and exports the quota_disk_used metric (as well as qtree metrics). Both collectors collect and export the same value for quota_disk_used
A small historical note: Most templates use the same name, but this one is slightly different. The ZAPI template was created a long time ago and did two things: collected qtree and quota metrics. When we started building a Rest template, we decided to seperate those metrics into their respective templates because that is clearer and allows customers to collect one without the other.
You said that you don't see quota_disk_used in VM, but you do see Rest:Quota collecting metrics? Can you paste the log line for one of the clusters that is exporting metrics for Rest:Quota? Here is an example time=2025-05-14T10:46:22.075-04:00 level=INFO source=collector.go:601 msg=Collected Poller=sar collector=Rest:Quota apiMs=126 bytesRx=28912 calcMs=0 exportMs=2 instances=44 instancesExported=484 metrics=440 metricsExported=506 numCalls=1 parseMs=1 pluginInstances=0 pluginMs=1 pollMs=128 renderedBytes=113842 zBegin=1747233981945
In this case, the Rest:Quota collector exported 484 quotas with 506 metrics. If I curl the poller's promPort, I see them like so:
curl -s 'http://127.0.0.1:12998/metrics' | rg -v '^#|^metadata' | sort
quota_disk_used{cluster="umeng-aff300-01-02",datacenter="dc-1",group="",qtree="trident_pvc_f86bbb72_ff49_444c_bfb6_e93f1b877cc3",svm="astra_300",type="tree",unit="kibibytes",user="",volume="trident_qtree_pool_trident_TIXRBILLKA"} 199608