-
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
The response time is too long #7
Comments
From @rverchere on January 6, 2018 17:10 Hi, this is due to ESX/Vcenter server which takes some time to provide all the data. The only thing you can do is to increment the scraping interval to 30 sec minimum |
From @ramonskie on January 24, 2018 10:4 it seems someone else solved it. |
From @rverchere on January 30, 2018 21:52 Hi, thanks @ramonskie, I'll give a try! |
Closing this as it should be resolved with the basic threading I added. |
From @peterzha on December 14, 2017 3:26
When I get the metrics by using the URL,the response usually continue for up to more than ten seconds.How to resolve this problem?
Copied from original issue: rverchere/vmware_exporter#22
The text was updated successfully, but these errors were encountered: