#Enable Top Clients/Files Metrics in Harvest #3904
1 messages · Page 1 of 1 (latest)
@meager bough Do you get any results if your curl below endpoint against ONTAP?
api/storage/volumes?fields=svm.name,name&activity_tracking.state=on
If you have enabled this after updating the template and restarting NABox, by default, new volumes affected by the activity tracking changes will be considered only after one hour by Harvest.
strange, no records:
{
"records": [
],
"num_records": 0,
"_links": {
"self": {
"href": "/api/storage/volumes?fields=svm.name,name&activity_tracking.state=on"
}
}
}
Ok. We need to fix this issue first.
vol analytics show -vserver netapp-proxmox
Scan
Vserver Volume State Progress Files Scanned Total Files
netapp-proxmox proxmox_backups on - - -
netapp-proxmox proxmox_backupserver on - - -
netapp-proxmox proxmox_linux_data on - - -
netapp-proxmox proxmox_linux_os on - - -
netapp-proxmox proxmox_windows_data on - - -
netapp-proxmox proxmox_windows_os on - - -
According to ONTAP Docu... this is all I need to do?
Oh weird ... with GUI option it enabled just now 🤔 I used CLI method.
Ah I used wrong one
These two flags seem similiar but do different things.
I used analytics 😵💫
Yeah i have tripped over them in past myself.
I can disable analytics then?
Yes
Thanks.
Also is this enough or do I need to enable for each cluster manually the "KeyPerf"?
cat harvest.yml
Defaults:
debug: false
addr: ""
collectors:
- Rest
- RestPerf
- KeyPerf
- Zapi
- ZapiPerf
- Ems
datacenter: ""
exporters:
- nabox-victoriametrics
enabled: false```
I just did now in defaults only.
By default, volume performance metrics will be collected via KeyPerf
I think NABox has collector at each cluster level so you will need to add in every cluster.
I'll move to Cluster section and see if it shows any data.
That shouldn't be needed though if you are making the change for TopClients
https://github.com/NetApp/harvest/blob/main/conf/restperf/default.yaml#L52
We use KeyPerf regardless
I have "No data" if it does not use KeyPerf 🤔
Guess I need to wait some time after enabling file tracking?
I think you are using harvest 26.02?
its the latest one that comes with 4.2.0
Are you getting data in curl now?
yes
yes curl shows data
ok restart NABox process once and if volume has traffic running data should be visible in 5-10 minutes post restart.
Yes, restarted 2min ago .... lets see.
Does system manager shows activity traffic?
That means I can undo KeyPerf changes? 🙂
Yes
I see some graphs now.
Cool
This needs to be removed then in latest version, its confusing 😄
Are you saying it's unclear, as if it's instructing people to enable this collector?
Correct.
Yeah we can remove that line and drive it via discussion link.
We'll make the change.
Or point it to this: https://docs.netapp.com/us-en/ontap-cli/volume-activity-tracking-on.html
We'll add this to discussion.
fyi.. After removing KeyPerf conf it does not display any graphs
Do you have any customization for RestPerf Volume template?
stopped
I did not create any RestPerf templates... only AuditLog and ChangeLog so far.
Please share support bundle here https://upload.nabox.org/yite-vuma-dire
Doc will be updated via PR https://github.com/NetApp/harvest/pull/4220/changes
And updated discussion https://github.com/NetApp/harvest/discussions/3904
So this means I still need the keyperf folder and everything?
Customization you still need.
Ah okay, I've did now everything except adding KeyPerf to harvest.yml .. lets see
Because thats the first step in your documentation ^^
I see, Let me test it once.
cool
But will wait for Top Clients ... this still shows "no data"
It can take couple of minutes as API we call provides data sometimes and sometimes it doesn't.
I have tested and yes KeyPerf needs to be listed in your default.yaml
Discussion steps are correct.
Yes please
I just enabled in defaults only not on cluster level, would be nice if this works out.
else each cluster is a pain when you got around 50 to manage 😛
Let me check test that also once 🙂
Tested, Listing in defaults does not work because NABox lists collectors at the cluster level, which causes the defaults to be overwritten at the cluster level.
@grave lance If this is something we can improve in NABox.
Now it works fine @fervent folio
cool. Thanks for confirming!
Documentation is right, just had to enable file tracking instead of analytics on Volume/SVM Level.
Yes.