-
Notifications
You must be signed in to change notification settings - Fork 680
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
Sub-second accuracy in syslog adapter #382
base: master
Are you sure you want to change the base?
Sub-second accuracy in syslog adapter #382
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine, do we need to have tests for this? Would it be better to somehow make this configurable?
@josegonzalez I'm new to contributing to logspout – are you asking me? I'm not super fluent in Go and the tests around the syslog adapter are a bit of the mystery to me at the moment. Making this opt-in with an environment variable should be super simple even for me, but I'm not sure if that's what you meant by "configurable". |
Could this be merged and release, please? |
Could this be merged and release, please? |
Btw this LGTM ... let me know if repo needs to announce call for co-maintainers. |
Yeah we should probably do that - I don't maintain the repo but Im sure there are folks that would want to. |
Other than unnecessarily losing timestamp accuracy, this breaks for syslog daemons that expect sub-second accuracy (like
fluentd
).