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

Handle how to encode data for different output sinks #3

Open
supernomad opened this issue Feb 27, 2017 · 0 comments
Open

Handle how to encode data for different output sinks #3

supernomad opened this issue Feb 27, 2017 · 0 comments

Comments

@supernomad
Copy link
Owner

So right now only protond is only capable of outputing the entire event structure as json encoded data. This is fine for testing and certain output sinks, however not all of them can support this data structure. The idea would be to allow for designating the final data and structure to send to the different outputs, and potentially allowing different outputs have different data encoding.

This could mean just having different output plugins for each of the different supported output sinks, but that means that any new sink will require direct development of protond. The idea would be to allow defining this structure during the filter process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant