-
Notifications
You must be signed in to change notification settings - Fork 64
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
Missing the milliseconds in Graylog #27
Comments
there's a merge request for this already: #23. Although I hardcoded the Not sure why it hasn't been merged yet though. |
Could you add time.Second.Nanoseconds() also for TLS branch? P.S. Maybe make sense to create branch v3 where to merge v2 and tls branches? |
After a quick look, it seems to me that the tls branch can easily be rebased on top of the current v2 branch, and merged afterwards - in my humble opinion, there's not even any need to cut a new release, as this would simply constitute an extension of the currently existing API, without any (breaking) changes in existing behaviour... gonna wait a bit though for the short vs. long message merge request (#34) to be accepted, as that one requires some editing of the tests introduced in tls. |
Great! |
Hello. I am waiting. |
Line 146 in message.go (v2.0 branch) is currently:
TimeUnix: float64(time.Now().Unix()),
Unix time is in seconds since 1.1.1970, thus, log entries in Graylog get the milliseconds truncated.
TimeUnix: float64(time.Now().UnixNano()) / float64(time.Second.Nanoseconds()),
works nicely.
Best regards.
The text was updated successfully, but these errors were encountered: