Skip to content
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

Microseconds support for date fields #4923

Closed
jojoob opened this issue Sep 11, 2015 · 3 comments
Closed

Microseconds support for date fields #4923

jojoob opened this issue Sep 11, 2015 · 3 comments
Labels
release_note:enhancement stalled Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@jojoob
Copy link

jojoob commented Sep 11, 2015

I've just turned on high precision timestamp in my rsyslog deamon and configured logstash to parse the events with SYSLOGBASE2 core grok pattern which writes the timestamp to the timestamp8601 field.

Kibana seems not be able to display a complete high precision timestamp (ISO8601) including microseconds. The dateFormat setting in Kibana has only the token SSS for milliseconds.

@rashidkpc
Copy link
Contributor

This requires support for 64bit integers: #1274

@timroes timroes added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Aug 17, 2018
@nreese
Copy link
Contributor

nreese commented Oct 2, 2020

@kertal Did support for nano seconds resolve this issue?

@kertal
Copy link
Member

kertal commented Oct 5, 2020

yes, this is now possible since data_nanos is supported in Elasticsearch & Kibana

https://www.elastic.co/guide/en/elasticsearch/reference/current/date_nanos.html

@nreese nreese closed this as completed Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:enhancement stalled Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

5 participants