-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance impact of refreshing each datastore info at every scrape #8
Comments
From @rverchere on September 13, 2017 9:55 Hi, yes I have the same issue, need to find another way to refresh datastore. |
From @wtip on September 13, 2017 14:25 My scrape interval is 60 seconds and after my discovery yesterday I changed the timeout from 10s to 30s.
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 @nivshlomokaltura on September 26, 2017 14:14 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 |
It appears this was removed. Let us know if you have any other issues with this. |
From @wtip on September 12, 2017 21:47
I've been running into an issue where one of my esxi hosts appears to be unreachable by the exporter.
I think what's actually happening is that the scrape is timing out.
The jump in scrape duration coincides with about the time that I deployed this code change #16
and it looks like I might be bumping up against my default 10 second timeout.
I've increased my timeout but I'm not sure if this is a great solution for everyone. Maybe the datastore refresh should be a configurable option.
Copied from original issue: rverchere/vmware_exporter#18
The text was updated successfully, but these errors were encountered: