Problem
The telegraf command line option --test is often misunderstood especially in that it does not send any data to the outputs but only to stdout. Therefore new users wonder why they don't see any data in their configured database(s) as they meant to use --once.
Proposal:
To improve the awareness for the user about the actual behavior when using --test I see the following options
- Keep
--test and add a (maybe red) output saying: "NOTE: Telegraf running in test mode, no data will be sent to the outputs!" or similar.
- Add a
--dry-run option disabling the output plugins. Used together with --once it resembles the present --test option. We can then remove --test. Additionally, the new option allows to run multiple gather cycles or listen for inputs with outputs disabled.
- Like 2 with the additional warning of 1.
What is your opinion on this?
Problem
The telegraf command line option
--testis often misunderstood especially in that it does not send any data to the outputs but only to stdout. Therefore new users wonder why they don't see any data in their configured database(s) as they meant to use--once.Proposal:
To improve the awareness for the user about the actual behavior when using
--testI see the following options--testand add a (maybe red) output saying: "NOTE: Telegraf running in test mode, no data will be sent to the outputs!" or similar.--dry-runoption disabling the output plugins. Used together with--onceit resembles the present--testoption. We can then remove--test. Additionally, the new option allows to run multiple gather cycles or listen for inputs with outputs disabled.What is your opinion on this?