-
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
inputs-vsphere did not complete within its interval #5296
Comments
Could you check if this still occurs in the nightly builds ? |
@danielnelson Thank you!.... I moved to below version as per your suggestion. Telegraf version:Telegraf unknown (git: master e95b88e) All graphs are generating little constant but, issue with CPU collection only which is missing for all esxi hosts |
It may be that you need to increase your collection interval, depending on how many values you are collecting and the amount of time it takes. One way to see how much time the plugin is taking is to enable the Can you also attach your configuration for this plugin? |
Please share your configuration file with us! Shorter collection interval than 60s is generally not recommended for vsphere. You may also want to increase collection concurrency. |
FYI: configured 4 VC which will have 500+ hosts all together. Even many time observed [inputs.vsphere]: Error in plugin: While collecting host: Post https://VC/sdk: context deadline exceeded FYI: It is not able to collect metrics where more number of hosts present. (having 2 VC where few number of hosts are present and which is showing constant graph) only issue is with larger inventory. Okay! here is the config file. [[outputs.influxdb]] urls = ["http://127.0.0.1:8086"] [[inputs.vsphere]] cluster_metric_include = [] datastore_metric_exclude = [ "*" ] |
I have the same issue with version 1.9.0.1、1.9.1.1,no problem with version 1.8.3-1. [global_tags] [[outputs.prometheus_client]] [[inputs.vsphere]] Here is the log: |
It looks like your interval is set to 15s. You need to increase that to at least 20s! If you truly need 20s granularity on your data, I recommend you do two things:
|
It works, thanks a lot |
No. it is not working only if including datastore metrics. |
As stated above, you need to declare a separate instance of the plugin and specify data stores, clusters and data centers in that instance with a 300s interval. |
According to your suggestion, real-time metrics are good, but non-real-time data can not get continuous data. |
What's the collection interval on the non real time metrics? It should be 300s or higher. Also, can you run with the -debug flag and send us logs? |
And yes, it might be because of a bug that's scheduled to be fixed in 1.10. You may want to try the latest nightly build from master and see if it fixes the issue. |
Yes! Data-collection interval But, below error observed in logs. and during this time, data is showing no value. |
Same Problem here ! Functional release
Not Functional release
I only get inputs-vsphere did not complete within its interval PROBLEM No graph is generated ! CONFIG
|
I having the same issue using this build: 1.9.4-1.x86_64.
|
@sunnybhatnagar Can you try with the latest nightly build? |
@danielnelson I have the same issue; just tried the nightly build and that fixes the issue! But now I got weird failed events in my vcenter, see: |
@MartVisser Can you open a new issue for that side effect? I'm going to close this issue, if anyone is having issues with the plugin not completing by the end of the interval please read the hints above and try again with the nightly builds. If you still have problems after that, please open a new issue. |
Relevant telegraf.conf:
System info:
CentOS Linux release 7.6.1810 (Core)
[Include Telegraf version, operating system name, and other relevant details]
Telegraf 1.9.2 (git: HEAD dda8079)
influxdb-1.7.2-1
Steps to reproduce:
Expected behavior:
Graph should be Constance
Actual behavior:
Additional info:
2019-01-16T13:41:10Z W! [agent] input "inputs.vsphere" did not complete within its interval
2019-01-16T13:41:20Z D! [outputs.influxdb] wrote batch of 28 metrics in 7.071246ms
2019-01-16T13:41:20Z D! [outputs.influxdb] buffer fullness: 0 / 10000 metrics.
2019-01-16T13:41:20Z W! [agent] input "inputs.vsphere" did not complete within its interval
[Include gist of relevant config, logs, etc.]
If i am restarting telegraf then, it is working fine for few minutes and again started with same error and no graph
The text was updated successfully, but these errors were encountered: