Skip to content
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] Deprecate force_discover_on_init #6860

Closed
prydin opened this issue Jan 6, 2020 · 1 comment · Fixed by #6861
Closed

[inputs.vsphere] Deprecate force_discover_on_init #6860

prydin opened this issue Jan 6, 2020 · 1 comment · Fixed by #6861
Milestone

Comments

@prydin
Copy link
Contributor

prydin commented Jan 6, 2020

Relevant telegraf.conf:

force_discover_on_init = false

System info:

Every version to date, every platform

Steps to reproduce:

  1. Set force_discover_on_init = false in the config file.

Expected behavior:

The intended behavior was that a partial metric collection was going to start prior to the first discovery completed.

Actual behavior:

Several unintended and unpredictable effects. Most of all, the flag was kind of useless, since no metric collection could take place before the first discovery was completed even if it ran in the background. Furthermore, the -test flag didn't work with the force_discover_on_init was set to false.

@danielnelson
Copy link
Contributor

The plugin may now produce some did not complete within its interval warnings on startup, but I plan to have parallel plugin startup implemented before the 1.14 release which will resolve this.

@danielnelson danielnelson added this to the 1.14.0 milestone Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants