Skip to content

Conversation

romanlevin
Copy link

Other than unnecessarily losing timestamp accuracy, this breaks for syslog daemons that expect sub-second accuracy (like fluentd).

Copy link
Member

@josegonzalez josegonzalez left a 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?

@romanlevin
Copy link
Author

romanlevin commented Feb 19, 2018

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".

@jrd
Copy link

jrd commented Dec 14, 2020

Could this be merged and release, please?

@TomasLukl
Copy link

Could this be merged and release, please?

@progrium
Copy link
Contributor

progrium commented Jul 3, 2023

Btw this LGTM ... let me know if repo needs to announce call for co-maintainers.

@josegonzalez
Copy link
Member

Yeah we should probably do that - I don't maintain the repo but Im sure there are folks that would want to.

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.

No milisecond on timestamps causes log ordering issues

6 participants