Performance impact of refreshing each datastore info at every scrape about vmware_exporter HOT 4 OPEN

Hi,

yes I have the same issue, need to find another way to refresh datastore.

from vmware_exporter.

My scrape interval is 60 seconds and after my discovery yesterday I changed the timeout from 10s to 30s.
Interestingly the average scrape duration also improved from around 3.5 seconds to 2.5 seconds after the change. My guess is that this has something to do with request blocking.
In the graph above the 1 node with a significantly higher scrape duration has 2 iscsi datastores instead of 1 so my guess is that the refresh duration increases with every datastore that is attached.

There's also the RefreshDatastore() method https://github.com/vmware/pyvmomi/blob/master/docs/vim/Datastore.rst maybe this is faster. This is not supported on the free esxi license. I got a 'Current license or ESXi version prohibits execution of the requested operation.',

I'm also wondering if there's a good way to make the refresh not block the rest of the request. I don't really care if the capacity info is refreshed before the request is returned. I just need it to be refreshed on a regular basis.

from vmware_exporter.

Hello,

Exporter is getting vcenter (5.5\6.0.2) to refresh datastore information as a vcenter task each query cycle and flood the task viewer.

i would suggest to remove ds.RefreshDatastoreStorageInfo() from vmware_exporter.py

from vmware_exporter.

This issue was moved to pryorda/vmware_exporter#8

from vmware_exporter.