#Add volume tiering policy and min_cooling_days to volume_labels
1 messages · Page 1 of 1 (latest)
Hi @cerulean spade what version of Harvest are you using? You should already see tiering.policy captured in volume labels. min_cooling_days is not currently collected. Let me check on that one
I am using 25.08.0, this is all i get when i send a request to prometheus:port/api/v1/query?query=volume_labels
"status": "success",
"data": {
"resultType": "vector",
"result": [
{
"metric": {
"__name__": "volume_labels",
"aggr": "<removed>",
"antiRansomwareState": "disabled",
"cluster": "<removed>",
"datacenter": "<removed>",
"instance": "<removed>",
"isDestinationCloud": "false",
"isDestinationOntap": "false",
"isEncrypted": "false",
"isHardwareEncrypted": "true",
"isProtected": "false",
"is_sis_volume": "true",
"is_space_enforcement_logical": "false",
"is_space_reporting_logical": "false",
"job": "aer-harvest01",
"junction_path": "<removed>",
"node": "<removed>",
"root_volume": "No",
"snaplock_type": "non_snaplock",
"snapshot_autodelete": "false",
"snapshot_policy": "none",
"state": "online",
"style": "flexvol",
"svm": "<removed>",
"svm_root": "false",
"type": "dp",
"volume": "<removed>"
},
"value": [1761659527, "1"
]
What if you try with a query like so volume_labels{tiering_policy!=""}
api/v1/query?query=volume_labels{tiering_policy!=""}
{"status":"success","data":{"resultType":"vector","result":[]},"stats":{"seriesFetched": "0","executionTimeMsec":8}}
are you sure that your volumes have a tiering policy? Looks like the volume needs to be in a FabricPool? Can you login to your cluster and check with volume show -fields tiering-policy Can you upload your poller logs for the poller in question to https://upload.nabox.org/wefi-mube-ciqu?
Maybe it was added in the recent nightlies? i can see tiering_policy was added to yaml on sept 8, https://github.com/NetApp/harvest/commit/fa1158137c5ceaaee85dffcd4f5b86e64a79d0b6
my bad! you're right, we did add that a couple of months ago
thanks for checking! Can you try a nightly to see if that works for you? I'll check on adding min_cooling_days
yes, we can add min_cooling_days to volume_labels as shown below
volume_labels{aggr="test1",antiRansomwareState="disabled",autosize_mode="",clone_parent_snapshot="",clone_parent_svm="",clone_parent_volume="",cluster="umeng-aff300-01-02",datacenter="dc-1",isDestinationCloud="false",isDestinationOntap="false",isEncrypted="false",isHardwareEncrypted="false",isProtected="false",is_sis_volume="",is_space_enforcement_logical="",is_space_reporting_logical="",junction_path="",node="umeng-aff300-01",root_volume="No",snaplock_type="non_snaplock",snapshot_autodelete="false",snapshot_policy="default",space_mgmt_try_first="",state="offline",style="flexvol",svm="svm1-mcc",svm_root="false",tags="",tiering_minimum_cooling_days="2",tiering_policy="snapshot_only",type="rw",volume="vol_test"} 1.0
Yes, i will try with nightly soon
I can share the template edits if you let me know what your ONTAP version is - that matters since there are two volume.yaml templates.
conf/rest/9.12.0/volume.yaml
conf/rest/9.14.0/volume.yaml
I am on 9.16
pull request opened to add min_cooling_days, if you want to apply these changes to your local nightly you can apply them from https://github.com/NetApp/harvest/pull/3977/files#diff-31679b30082f58fe0dfc3df1f9986be7d2924be45243275d1da94b9e39f739bf