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

WIP: Support graphite line-protocol in exec plugin. #655

Merged
merged 2 commits into from
Feb 9, 2016
Merged

Conversation

sparrc
Copy link
Contributor

@sparrc sparrc commented Feb 6, 2016

Generally normalize the data formats supported in Telegraf and make a generic plugin-like interface for writing new ones.

@sparrc sparrc changed the title Support graphite line-protocol in exec plugin. WIP: Support graphite line-protocol in exec plugin. Feb 6, 2016
@sparrc
Copy link
Contributor Author

sparrc commented Feb 6, 2016

TODO:

  • finish general DATA_FORMAT.md document
  • document how to write an input that accepts generic data formats
  • unit test JSON parser
  • unit test Graphite parser
  • unit test Influx parser
  • Support ad-hoc parsers in kafka_consumer input plugin

@sparrc sparrc force-pushed the henrypfhu-master branch 22 times, most recently from 45f8881 to 2d501ed Compare February 7, 2016 02:24
@sparrc sparrc mentioned this pull request Feb 7, 2016
@sparrc sparrc force-pushed the henrypfhu-master branch 3 times, most recently from 225cb94 to 4877bdb Compare February 9, 2016 00:10
@sparrc sparrc force-pushed the henrypfhu-master branch 15 times, most recently from 8348ad2 to 0064cc2 Compare February 9, 2016 03:07
This constitutes a large change in how we will parse different data
formats going forward (for the plugins that support it)

This is working off @henrypfhu's changes.
@sparrc sparrc merged commit e619493 into master Feb 9, 2016
@sparrc sparrc deleted the henrypfhu-master branch February 9, 2016 04:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants