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.

Sign up for GitHub

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

Jump to bottom

Trouble with millisecond (or any sub-second) resolution (outdated protocol implementation?) #165

Open

costa opened this issue Feb 1, 2020 · 0 comments

costa commented Feb 1, 2020

First, thanks for maintaining this module.

Then, it appears to have trouble with getting sub-second resolution right, and it may be because the last update of the related code (#47, 2016) doesn't seem to conform to the current fluentd spec (https://github.com/fluent/fluentd/wiki/Forward-Protocol-Specification-v1, 2017).

I've checked this with a new project having the most recent versions of everything:

second resolution works fine
millisecond resolution yields invalid dates
fluentd is barely configured
other components (e.g. a ruby one with a "standard" client lib) perform as expected (with nanosecond resolution).

I believe it's a quick fix for @sveneh or @okkez or other people doing great job here.

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