hi team, I have a customer who is using Harvest to collect stats from ONTAP 9.8 systems. They recently ran into an issue where after a new qtree was provisioned, the quota reports (qtree_disk_limit, qtree_disk_used, etc) were not captured until the customer restarted Harvest. Don't know if this is an one-time occurrence or not - customer is attempting to reproduce the issue in their lab. Curious to know if someone here might have run across this before and any suggestions what to do. Thank you!
#Qtree quota report stats
1 messages · Page 1 of 1 (latest)
@scenic hill Which version of Harvest customer is using?
In your example, quota reports metrics are collected through Zapi collector.
Till Harvest version 22.08, Harvest Zapi Collector captures any new object within 10 minutes of its creation. This was driven by instance configuration in zapi default.yaml here https://github.com/NetApp/harvest/blob/release/22.05.0/conf/zapi/default.yaml#L6
From Harvest version 22.11 onwards, Harvest Zapi Collector captures any new object during next data poll of its creation in ONTAP. Default data poll schedule is 3 minutes.
https://github.com/NetApp/harvest/blob/release/22.11.0/conf/zapi/default.yaml#L6
ZapiPerf collector still captures new object within 10 minutes of its creation in Harvest.
I thin kin @scenic hill case, the customer actually let it run for a while. Correct @scenic hill ?
customer is running harvest-21.11.1-1. Yann is correct, the customer waited 2 days. One thing I did find out from the PS team that helped set this up was that the customer didn't deploy Harvest with a time series DB. The customer has their own TS DB and just makes API to Harvest for the metric collections. not sure if this has any impacts.
@scenic hill looks like customer is on a very old version. Could you suggest customer to upgrade to latest release which is 22.11.1 https://github.com/NetApp/harvest/releases/tag/v22.11.1
We have had an issue (https://github.com/NetApp/harvest/issues/1224) with quota object collection in old releases which is fixed in 22.11. Most likely customer is hitting this issue.
thank you Rahul. would this https://github.com/NetApp/harvest/issues/1640 be the better bug to share with the customer?
Yes this is also same.