lapis steppe
After upgrading to 24.08, we see warnings like this
2024-08-29T14:32:12Z WRN rest/rest.go:591 > This instance is already processed. instKey is not unique Poller=flc1-noprod-ash-storage collector=Rest:Quota instKey=2305843013508661248
Seems not all metrics are collected due to this warning.
│ 7 pluginInstances=0 pluginMs=8 pollMs=1683 zBegin=1724942831126 ```
Also in the Quota Dashboard, The number of qtrees is much lower than the actual number. Some fields show as -1%.
obsidian yoke
@lapis steppe Can you run this CLI command to get the quotas and share the quota.txt file result to us at ng-harvest-files@netapp.com?
./bin/harvest rest -p POLLER_NAME show data --api storage/quota/reports > quota.txt
lapis steppe
@obsidian yoke will email to you
gray inlet
received
lapis steppe
we have 9.14 and 9.10 clusters. see this warning on both
lapis steppe
@gray inlet BTW, will you guys go to Insight next month? It will be great to meet you there.
gray inlet
@lapis steppe I'm hopefully we'll be able to send someone, but not sure yet
gray inlet
hi @lapis steppe we thought that index was sufficient to uniquely identify quotas based on what swagger says. Your quota.txt clearly shows that is not the case. 🙂 We'll add a unit test for this problem and fix the issue.
In the meantime, can you try updating your conf/rest/9.12.0/quota.yaml template by adding the following at line 9
- ^^volume.uuid => volume_uuid
restart the poller, and let use know if that removes the warnings?
lapis steppe
Sorry. I am out. Will be back next Wednesday. Will test then. Thanks!
warm hazel
@lapis steppe Fix for this issue is now available in Harvest nightly build https://github.com/NetApp/harvest/releases/tag/nightly
Please let us know if this fixes the issue.
lapis steppe
@warm hazel confirming it's fixed in the nightly build. thanks!