-
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
Telegraf Ignores The Failed Input Requirement #11289
Comments
Hello! I recommend posting this question in our Community Slack or Community Page, we have a lot of talented community members there who could help answer your question more quickly. You can also learn more about Telegraf by enrolling at InfluxDB University for free! Heads up, this issue will be automatically closed after 7 days of inactivity. Thank you! |
Duplicate of #10694. Please continue the discussion there. |
* add ignore_init_fail_input option for ignore initialization failed Input influxdata#11289 influxdata#10694 * rename option ignore_init_fail_input to ignore_error_inputs
Background
When telegraf starts, the Inputs will be initialized. If the initialization fails, telegraf will exit the program directly. This leads to the process of automatic monitoring. If there is an error in one input, all input additions on the machine will fail.
Our process is as follows:
New Server —> create telegraf conf to telegraf.d —> restart telegraf
example:
new monogodb —> create mongodb.conf to telegraf.d — restart telegraf
new docker container —> create docker.conf to telegraf.d — restart telegraf
In this process, the monitoring of the same machine uses the same telegraf systemd.
When there is an input init exception (for example: the mongodb process is gone, the mongodb input init fails), telegraf will fail to start.
Why don't we start multiple telegraf processes to monitor their own programs?
Because we may install multiple programs on one machine, this involves the problem of excessive resource consumption.
After all, monitoring is very sensitive to resource usage, and we hope that a machine only needs to start a telegraf.
Demand
We would like to be able to add a configuration that sets whether it ignores input that fails init.
If it is true, when the telegraf is loading, if the input initialization is abnormal, the exception log will be logged directly, ignore it and continue to execute other inputs.
Hope to hear from you, thanks
The text was updated successfully, but these errors were encountered: