How to get tiering usage data? #2228
-
Hello CLI
API (may be..?)
{
"records": [
{
"uuid": "18ed9a59-26e5-11ee-a15c-710ff4588dd1",
"name": "nfs_Vol",
"svm": {
"name": "FsxN",
"uuid": "f4df1cdb-26e4-11ee-a15c-710ff4588dd1",
"_links": {
"self": {
"href": "/api/svm/svms/f4df1cdb-26e4-11ee-a15c-710ff4588dd1"
}
}
},
"space": {
"capacity_tier_footprint": 0
},
"_links": {
"self": {
"href": "/api/storage/volumes/18ed9a59-26e5-11ee-a15c-710ff4588dd1"
}
}
},
{
"uuid": "5e531b2f-26fa-11ee-a15c-710ff4588dd1",
"name": "cifs_Vol",
"svm": {
"name": "FsxN",
"uuid": "f4df1cdb-26e4-11ee-a15c-710ff4588dd1",
"_links": {
"self": {
"href": "/api/svm/svms/f4df1cdb-26e4-11ee-a15c-710ff4588dd1"
}
}
},
"space": {
"capacity_tier_footprint": 0
},
"_links": {
"self": {
"href": "/api/storage/volumes/5e531b2f-26fa-11ee-a15c-710ff4588dd1"
}
}
},
{
"uuid": "9c470c4b-26ea-11ee-a15c-710ff4588dd1",
"name": "vol1",
"svm": {
"name": "FsxN",
"uuid": "f4df1cdb-26e4-11ee-a15c-710ff4588dd1",
"_links": {
"self": {
"href": "/api/svm/svms/f4df1cdb-26e4-11ee-a15c-710ff4588dd1"
}
}
},
"space": {
"capacity_tier_footprint": 0
},
"_links": {
"self": {
"href": "/api/storage/volumes/9c470c4b-26ea-11ee-a15c-710ff4588dd1"
}
}
},
{
"uuid": "f25c133d-26e8-11ee-a15c-710ff4588dd1",
"name": "cifs_Vol2",
"svm": {
"name": "FsxN",
"uuid": "f4df1cdb-26e4-11ee-a15c-710ff4588dd1",
"_links": {
"self": {
"href": "/api/svm/svms/f4df1cdb-26e4-11ee-a15c-710ff4588dd1"
}
}
},
"space": {
"capacity_tier_footprint": 0
},
"_links": {
"self": {
"href": "/api/storage/volumes/f25c133d-26e8-11ee-a15c-710ff4588dd1"
}
}
},
{
"uuid": "f52e8271-26e4-11ee-ae01-6ddd05c78c3c",
"name": "FsxN_root",
"svm": {
"name": "FsxN",
"uuid": "f4df1cdb-26e4-11ee-a15c-710ff4588dd1",
"_links": {
"self": {
"href": "/api/svm/svms/f4df1cdb-26e4-11ee-a15c-710ff4588dd1"
}
}
},
"space": {
"capacity_tier_footprint": 0
},
"_links": {
"self": {
"href": "/api/storage/volumes/f52e8271-26e4-11ee-ae01-6ddd05c78c3c"
}
}
}
],
"num_records": 5,
"_links": {
"self": {
"href": "/api/storage/volumes?fields=space.capacity_tier_footprint,svm"
}
}
} so i tried to modify |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
This is the mapping of the requested ONTAP zapi, cli and rest is as per below.
Below steps are for REST collector volume object.
|
Beta Was this translation helpful? Give feedback.
-
Hello
|
Beta Was this translation helpful? Give feedback.
-
As per the Ontap REST docs, these fields were already been added in 9.8 release. Sure, I am sharing the Zapi side changes for collecting the same metrics. Below steps are for ZAPI collector for
Note: Just to check first that 9.8.0 cluster which you have tested would shows data in CLI |
Beta Was this translation helpful? Give feedback.
-
Hi The aggr attribute doesn't seem to be included.
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
As per the Ontap REST docs, these fields were already been added in 9.8 release.
Sure, I am sharing the Zapi side changes for collecting the same metrics.
As this is using different api
volume-footprint-get-iter
thanvolume-get-iter
, We won't be extendingvolume.yaml
file here.Below steps are for ZAPI collector for
volume_footprint
object.We are going to create a new template and add it to your
custom.yaml
. In the commands below, Harvest is installed in/opt/harvest
.Adjust as needed.
vi /opt/harvest/conf/zapi/custom.yaml
.custom.yaml
already exists then add theVolumeFootprint
line under theobjects:
section.