-
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 doesn't error on unused #12000
Comments
Looks like v1.23.4 is the last working version as well. My local v1.24.0 and v1.24.1 builds both failed. Here is the diff from v1.23.4 to v1.24.0: @Hipska also pointed out that there is a test for unused fields, but when running telegraf it is not present 3ad9fe7 is the commit that breaks this behavior. The previous commits that day ff17ede and fd84042 both correctly fail on start. |
ok I know where it is not correctly calling However, in the old code, the miss count threshold could either be 0 or 1 depending on different scenarios. @srebhan sorry to ping you on yet another one, I need to dig into this further, but maybe you know why it was hardcoded in the new version? |
I just tested, but even with 2 or 3 unknown extra config parameters, no error/warning is given.. |
I wasted so much time due to this :( |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.24.0
Docker
No response
Steps to reproduce
Expected behavior
Actual behavior
No relevant error observed.
Additional info
Works as expected in telegraf 1.23.4
The text was updated successfully, but these errors were encountered: