-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[input.vsphere] Option query for maxQueryMetrics failed. Using default #5034
Comments
This is benign. It just means that the plugin didn't find a en explicit setting for maxQueryMetrics and that it's using the default instead. This should have been a debug log instead of an informational-level log. We will address this in the next PR. |
I have the same issue.
|
That's not true. Even with the explicit setting in the input config, it throws this error. |
You will see the message even if you've configured it in the config file. That's the correct behavior. It will query for the setting in vCenter to make sure you haven't specified a value that's higher than what the vCenter can handle. What's NOT correct is that it should have been a DEBUG message instead of an INFO. This will be fixed in 1.9.1. |
Closing as it looks like this was resolved in #5113 |
Relevant telegraf.conf:
System info:
[Include Telegraf version, operating system name, and other relevant details]
Latest Telegraf version
Ubuntu 16.04
vSphere Client version 6.7.0
Steps to reproduce:
Expected behavior:
No warnings
Actual behavior:
[input.vsphere] Option query for maxQueryMetrics failed. Using default
Additional info:
[Include gist of relevant config, logs, etc.]
I think I this issue describes mine but there's no solution.
The text was updated successfully, but these errors were encountered: