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

Implement a Syslog Source #165

Open
blt opened this issue Dec 26, 2016 · 4 comments
Open

Implement a Syslog Source #165

blt opened this issue Dec 26, 2016 · 4 comments

Comments

@blt
Copy link
Collaborator

blt commented Dec 26, 2016

Cernan could be a pretty decent syslog. But! We've to date assumed that you'll pipe logs in by dropping them on disk first. Maybe we oughtn't.

@tfheen
Copy link
Contributor

tfheen commented Jun 5, 2017

https://crates.io/crates/syslog_rfc5424 + a UDP and TCP listener shouldn't be terribly hard to put together. Might want to support more syslog formats later too.

@blt
Copy link
Collaborator Author

blt commented Jun 5, 2017

@tfheen I'd be very interested to see this work done. syslog_rfc5424 would need updating, I think. rustc_serialize is deprecated in favor of serde but the update shouldn't be a nightmare show.

@tfheen
Copy link
Contributor

tfheen commented Jun 20, 2017

I've started looking slightly at this, and since I'd like to support the various syslog formats, I'm looking at nom. Thoughts, opinions, etc?

@blt
Copy link
Collaborator Author

blt commented Jun 20, 2017

I think that'd be a perfect use-case for nom. I've used nom in past days to parse in the statsd and graphite sources, backing it out for something hand-rolled since those formats are simple enough. Syslog seems like it hits the sweet-spot of complexity for using nom.

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

2 participants