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

easier plugin testing without outputs #1820

Closed
rubycut opened this issue Sep 28, 2016 · 1 comment
Closed

easier plugin testing without outputs #1820

rubycut opened this issue Sep 28, 2016 · 1 comment
Labels
feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin help wanted Request for community participation, code, contribution

Comments

@rubycut
Copy link
Contributor

rubycut commented Sep 28, 2016

I should be able to test plugins without without any outputs, that is the whole point of testing, currently it is not possible.

telegraf -test -config-directory . -input-filter http_response
2016/09/28 10:14:42 Using config file: /etc/telegraf/telegraf.conf
2016/09/28 10:14:42 Error: no outputs found, did you provide a valid config file?
@sparrc sparrc added feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin help wanted Request for community participation, code, contribution labels Sep 28, 2016
@nhaugo nhaugo added this to the Future Milestone milestone Sep 28, 2016
ingosus added a commit to ingosus/telegraf that referenced this issue Feb 20, 2017
ingosus added a commit to ingosus/telegraf that referenced this issue Feb 20, 2017
@danielnelson
Copy link
Contributor

Implemented in #2446

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin help wanted Request for community participation, code, contribution
Projects
None yet
Development

No branches or pull requests

4 participants