-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support nanosecond (epoch nano) timestamp #9
Comments
Currently, Elsaticsearch does not handle micro and nano-second precision. |
I agree, Elasticsearch only handles millsecs but the plugin doesn't handles the cases where the We could simply convert the epoch nano to epoch milli and create the |
Actually, it should handle microseconds and nanoseconds (as well as seconds and millisecs) |
fixed as of 0.2.6 |
@ecwws @cosmo0920 thank you! 😄 |
Since fluentd supports nanosecond timestamp, could we extend this plugin to support epoch nano as well?
We have one source that currently set
timestamp
field to epoch nano, so at the moment we need to do a transformation to millisecs, would be nice if the plugin supported it out-of-the-box.The text was updated successfully, but these errors were encountered: