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

Some plugin errors not logged/logged at debug level with Telegraf 1.12.5 #6666

Closed
danielnelson opened this issue Nov 16, 2019 · 0 comments · Fixed by #6665
Closed

Some plugin errors not logged/logged at debug level with Telegraf 1.12.5 #6666

danielnelson opened this issue Nov 16, 2019 · 0 comments · Fixed by #6665
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Milestone

Comments

@danielnelson
Copy link
Contributor

Many plugin errors are not being logged at the error level and instead are being logged at debug level.

Relevant telegraf.conf:

Many configurations that will produce an error:

[[inputs.influxdb]]
  urls = ["http://wrong.local:8086/debug/vars"]

System info:

Telegraf 1.12.5

Steps to reproduce:

  1. Run Telegraf with a plugin that will produce an error.

Expected behavior:

Error emitted from influxdb input due to the wrong hostname.

E! [inputs.influxdb] Error in plugin: [url=http://wrong.local:8086/debug/vars]: Get http://wrong.local:8086/debug/vars: dial tcp: lookup wrong.local: no such host

Actual behavior:

Error appears not to be logged at first, and is instead logged at debug level:

D! [inputs.influxdb] Error in plugin: [url=http://wrong.local:8086/debug/vars]: Get http://wrong.local:8086/debug/vars: dial tcp: lookup wrong.local: no such host
@danielnelson danielnelson added bug unexpected problem or unintended behavior regression something that used to work, but is now broken labels Nov 16, 2019
@danielnelson danielnelson added this to the 1.12.6 milestone Nov 16, 2019
@danielnelson danielnelson pinned this issue Nov 16, 2019
@danielnelson danielnelson unpinned this issue Nov 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant