Hi @DARREN_REED,
You can set the update frequency on a perf object basis in the collection template but I would probably set it on a per poller basis in netapp-harvest.conf. The reason is if you start tweaking update frequency of individual objects you will likely still run out of time and get some skipped polls on minute boundaries where everything needs to be collected. So I would prefer to disable collection of objects with a high API time that are non-essential, or change the overall polling interval to be something higher. You could also split into two pollers, with two different collection templates and update frequenceies, to maximize data collected and minimize skips. Personally I would just increase the polling frequency to a 2 or 3 or 5 minutes at the poller level and see how that goes.
Also remember that graphite db files are created according to the settings in storage-schemas.conf the first time the metric comes in. So if you will manage different frequencies you should also modify the storage-schemas.conf file and resize any existing graphite db files to match it. If you don't update the graphite db settings you will just use more diskspace to store them but otherwise Grafana, with the default 'collected line mode', will just connect your valid data points and skip the null values not being sent.
Hope this helps.
Cheers,
Chris Madden
Storage Architect, NetApp EMEA (and author of Harvest)
Blog: It all begins with data
P.S. Please select “Options” and then “Accept as Solution” if this response answered your question so that others will find it easily!