# Can't get high granularity for a timestamp

**URL:** <https://discuss.elastic.co/t/cant-get-high-granularity-for-a-timestamp/95564>\
**Category:** Logstash\
**Created:** [August 2, 2017, 3:16pm UTC](https://discuss.elastic.co/t/cant-get-high-granularity-for-a-timestamp/95564 "2017-08-02T15:16:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dboss101](https://avatars.discourse-cdn.com/v4/letter/d/7993a0/32.png) [@dboss101](https://discuss.elastic.co/u/dboss101)\
**Post date:** [August 2, 2017, 3:16pm UTC](https://discuss.elastic.co/t/cant-get-high-granularity-for-a-timestamp/95564/1 "2017-08-02T15:16:01Z")

</div>

Hey everyone,

in one of our use cases with elastic, we're sending logs to it... as most people do.  
and it seems that the timestamp is limited only to 3 digits in the miliseconds (and lower) space, but we want to have higher granularity than that.  
I've tried to use something like the following conf in the screenshot to make it happen but to no avail.

 ![1](https://us1.discourse-cdn.com/elastic/original/3X/3/a/3ac55c1d8b67ed11e845ce6bbb86fc6cf8b02e46.PNG)

then got to this super old bug that seems to be still valid?..?  
[https://logstash.jira.com/browse/LOGSTASH-1585](https://logstash.jira.com/browse/LOGSTASH-1585)

please advice if there is a way to make the timestamp show microseconds...

thanks!

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 2, 2017, 5:39pm UTC](https://discuss.elastic.co/t/cant-get-high-granularity-for-a-timestamp/95564/2 "2017-08-02T17:39:33Z")

</div>

The date data type in Elasticsearch is limited to millisecond resolution, so right now there's no workaround unless you want to store the microseconds (or whatever resolution you want) in a separate field.

---

<div class="post-metadata">

**Author:** ![dboss101](https://avatars.discourse-cdn.com/v4/letter/d/7993a0/32.png) [@dboss101](https://discuss.elastic.co/u/dboss101)\
**Post date:** [August 3, 2017, 7:40am UTC](https://discuss.elastic.co/t/cant-get-high-granularity-for-a-timestamp/95564/3 "2017-08-03T07:40:00Z")

</div>

this limitation you mention is in the docs?  
and do you have an idea if there is an open feature request to change that limitation?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 3, 2017, 8:06am UTC](https://discuss.elastic.co/t/cant-get-high-granularity-for-a-timestamp/95564/4 "2017-08-03T08:06:18Z")

</div>

> this limitation you mention is in the docs?

Yes. It's mentioned in one of the first paragraphs in the date data type docs.

> and do you have an idea if there is an open feature request to change that limitation?

I have no idea but I would assume so.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 31, 2017, 8:06am UTC](https://discuss.elastic.co/t/cant-get-high-granularity-for-a-timestamp/95564/5 "2017-08-31T08:06:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.