Skip to content

telegraf doesn't report in which file there is an error #944

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.

Sign up for GitHub

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

Jump to bottom
Closed
rubycut opened this issue Mar 31, 2016 · 1 comment
Closed

telegraf doesn't report in which file there is an error #944

rubycut opened this issue Mar 31, 2016 · 1 comment
Labels
bug unexpected problem or unintended behavior

Comments

@rubycut
Copy link
Contributor

rubycut commented Mar 31, 2016

In case of having multiple config files, filename is not reported, only line number:

telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/telegraf/telegraf.d -test
2016/03/31 04:20:40 toml: line 5: parse error
@rubycut rubycut changed the title telegraf doesn't report in which file there is error telegraf doesn't report in which file there is an error Mar 31, 2016
@sparrc sparrc added the bug unexpected problem or unintended behavior label Mar 31, 2016
sparrc added a commit that referenced this issue Apr 1, 2016
@sparrc
Cleanup & standardize config file
ee74f8c 
changes:

- -sample-config will now comment out all but a few default plugins.
- config file parse errors will output path to bad conf file.
- cleanup 80-char line-length and some other style issues.
- default package conf file will now have all plugins, but commented
  out.

closes #199
closes #944
@sparrc
Copy link
Contributor

sparrc commented Apr 1, 2016

thanks for the report, I was working on some config file things anyways so I'll get a fix for this in with #948

sparrc added a commit that referenced this issue Apr 1, 2016
@sparrc
Cleanup & standardize config file
bf447bf 
changes:

- -sample-config will now comment out all but a few default plugins.
- config file parse errors will output path to bad conf file.
- cleanup 80-char line-length and some other style issues.
- default package conf file will now have all plugins, but commented
  out.

closes #199
closes #944
sparrc added a commit that referenced this issue Apr 1, 2016
@sparrc
Cleanup & standardize config file
10658cb 
changes:

- -sample-config will now comment out all but a few default plugins.
- config file parse errors will output path to bad conf file.
- cleanup 80-char line-length and some other style issues.
- default package conf file will now have all plugins, but commented
  out.

closes #199
closes #944
sparrc added a commit that referenced this issue Apr 1, 2016
@sparrc
Cleanup & standardize config file
2e75535 
changes:

- -sample-config will now comment out all but a few default plugins.
- config file parse errors will output path to bad conf file.
- cleanup 80-char line-length and some other style issues.
- default package conf file will now have all plugins, but commented
  out.

closes #199
closes #944
@sparrc sparrc closed this as completed in e436b2d Apr 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rubycut @sparrc