# Timestamps stored as seconds since Unix epoch **URL:** \ **Category:** Elasticsearch\ **Created:** [March 29, 2015, 2:17pm UTC](https://discuss.elastic.co/t/timestamps-stored-as-seconds-since-unix-epoch/22971 "2015-03-29T14:17:10Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Jean\_Marc\_Saffroy](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@Jean\_Marc\_Saffroy](https://discuss.elastic.co/u/Jean_Marc_Saffroy)\ **Post date:** [March 29, 2015, 2:17pm UTC](https://discuss.elastic.co/t/timestamps-stored-as-seconds-since-unix-epoch/22971/1 "2015-03-29T14:17:10Z")
Hi all, Not sure what I'm doing wrong, but I couldn't find a way to store my docs with timestamps as seconds since the Unix epoch and query them properly. I have my date/time field mapped like this: "start\_time": {"type": "date" }, I store documents like this: { "start\_time": 1427631731, ... } And get no result when I do a range query like this: ``` "query": { "range": { "@timestamp": { "gte": "2015-03-29" }} } ``` I have good results when I store timestamps as strings in ISO format. Is that supposed to work? Is there a specific date parser I should use? JM -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALZqptaAcQ%3DtC2s1HPNeh%2BrpD5UdT\_rRvvFcjNFPXQ%2Bt3SbEqA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALZqptaAcQ%3DtC2s1HPNeh%2BrpD5UdT_rRvvFcjNFPXQ%2Bt3SbEqA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jean\_Marc\_Saffroy](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@Jean\_Marc\_Saffroy](https://discuss.elastic.co/u/Jean_Marc_Saffroy)\ **Post date:** [March 29, 2015, 2:18pm UTC](https://discuss.elastic.co/t/timestamps-stored-as-seconds-since-unix-epoch/22971/2 "2015-03-29T14:18:53Z")
Of course I left a typo in my email: I do use the same field name across mapping def, docs and queries, and it does not work. JM On Sun, Mar 29, 2015 at 4:17 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) wrote: > Hi all, > > Not sure what I'm doing wrong, but I couldn't find a way to store my docs > with timestamps as seconds since the Unix epoch and query them properly. I > have my date/time field mapped like this: > > "start\_time": {"type": "date" }, > > I store documents like this: > > { "start\_time": 1427631731, ... } > > And get no result when I do a range query like this: > > ``` > "query": { > "range": { "@timestamp": { "gte": "2015-03-29" }} > } > > ``` > > I have good results when I store timestamps as strings in ISO format. > > Is that supposed to work? Is there a specific date parser I should use? > > JM -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALZqptZ16diE%2BOuChEKcYLu%2BwXL2ernqtOos3qDr6svvtkhMuw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALZqptZ16diE%2BOuChEKcYLu%2BwXL2ernqtOos3qDr6svvtkhMuw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jean\_Marc\_Saffroy](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@Jean\_Marc\_Saffroy](https://discuss.elastic.co/u/Jean_Marc_Saffroy)\ **Post date:** [March 29, 2015, 3:12pm UTC](https://discuss.elastic.co/t/timestamps-stored-as-seconds-since-unix-epoch/22971/3 "2015-03-29T15:12:43Z")
Here is a curl recreation, hopefully that will be clearer: > **[\#!/bin/bashset -xcurl -X DELETE 'http://localhost:9200/test-foo?pretty' -...](https://pastebin.com/DUhbpgze)** > > Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time. JM On Sun, Mar 29, 2015 at 4:18 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) wrote: > Of course I left a typo in my email: I do use the same field name across > mapping def, docs and queries, and it does not work. > > JM > > On Sun, Mar 29, 2015 at 4:17 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) wrote: > > > Hi all, > > > > Not sure what I'm doing wrong, but I couldn't find a way to store my docs > > with timestamps as seconds since the Unix epoch and query them properly. I > > have my date/time field mapped like this: > > > > "start\_time": {"type": "date" }, > > > > I store documents like this: > > > > { "start\_time": 1427631731, ... } > > > > And get no result when I do a range query like this: > > > > ``` > > "query": { > > "range": { "@timestamp": { "gte": "2015-03-29" }} > > } > > > > ``` > > > > I have good results when I store timestamps as strings in ISO format. > > > > Is that supposed to work? Is there a specific date parser I should use? > > > > JM -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP\_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 29, 2015, 8:21pm UTC](https://discuss.elastic.co/t/timestamps-stored-as-seconds-since-unix-epoch/22971/4 "2015-03-29T20:21:31Z")
Unix epoch isn't a supported format. Take a look at > **[format | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-date-format.html)** On 30 March 2015 at 02:12, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) wrote: > Here is a curl recreation, hopefully that will be clearer: > [#!/bin/bashset -xcurl -X DELETE 'http://localhost:9200/test-foo?pretty' - Pastebin.com](http://pastebin.com/DUhbpgze) > > JM > > On Sun, Mar 29, 2015 at 4:18 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) wrote: > > > Of course I left a typo in my email: I do use the same field name across > > mapping def, docs and queries, and it does not work. > > > > JM > > > > On Sun, Mar 29, 2015 at 4:17 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) > > wrote: > > > > > Hi all, > > > > > > Not sure what I'm doing wrong, but I couldn't find a way to store my > > > docs with timestamps as seconds since the Unix epoch and query them > > > properly. I have my date/time field mapped like this: > > > > > > "start\_time": {"type": "date" }, > > > > > > I store documents like this: > > > > > > { "start\_time": 1427631731, ... } > > > > > > And get no result when I do a range query like this: > > > > > > ``` > > > "query": { > > > "range": { "@timestamp": { "gte": "2015-03-29" }} > > > } > > > > > > ``` > > > > > > I have good results when I store timestamps as strings in ISO format. > > > > > > Is that supposed to work? Is there a specific date parser I should use? > > > > > > JM > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP\_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP\_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU\_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jean\_Marc\_Saffroy](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@Jean\_Marc\_Saffroy](https://discuss.elastic.co/u/Jean_Marc_Saffroy)\ **Post date:** [March 29, 2015, 10:16pm UTC](https://discuss.elastic.co/t/timestamps-stored-as-seconds-since-unix-epoch/22971/5 "2015-03-29T22:16:03Z")
I thought I might have missed something, and it surprises me that the Unix epoch isn't supported! Well, I guess I'll have to work around that. Thanks! JM On Sun, Mar 29, 2015 at 10:21 PM, Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com) wrote: > Unix epoch isn't a supported format. Take a look at > [format | Elasticsearch Guide [8.11] | Elastic](http://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-date-format.html) > > On 30 March 2015 at 02:12, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) wrote: > > > Here is a curl recreation, hopefully that will be clearer: > > [#!/bin/bashset -xcurl -X DELETE 'http://localhost:9200/test-foo?pretty' - Pastebin.com](http://pastebin.com/DUhbpgze) > > > > JM > > > > On Sun, Mar 29, 2015 at 4:18 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) > > wrote: > > > > > Of course I left a typo in my email: I do use the same field name across > > > mapping def, docs and queries, and it does not work. > > > > > > JM > > > > > > On Sun, Mar 29, 2015 at 4:17 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) > > > wrote: > > > > > > > Hi all, > > > > > > > > Not sure what I'm doing wrong, but I couldn't find a way to store my > > > > docs with timestamps as seconds since the Unix epoch and query them > > > > properly. I have my date/time field mapped like this: > > > > > > > > "start\_time": {"type": "date" }, > > > > > > > > I store documents like this: > > > > > > > > { "start\_time": 1427631731, ... } > > > > > > > > And get no result when I do a range query like this: > > > > > > > > ``` > > > > "query": { > > > > "range": { "@timestamp": { "gte": "2015-03-29" }} > > > > } > > > > > > > > ``` > > > > > > > > I have good results when I store timestamps as strings in ISO format. > > > > > > > > Is that supposed to work? Is there a specific date parser I should use? > > > > > > > > JM > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP\_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP\_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU\_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU\_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALZqptbGPcQDxUaFHfRfttdGyzFKVUogZEenj3nAPxOJYWitCw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALZqptbGPcQDxUaFHfRfttdGyzFKVUogZEenj3nAPxOJYWitCw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 31, 2015, 6:58am UTC](https://discuss.elastic.co/t/timestamps-stored-as-seconds-since-unix-epoch/22971/6 "2015-03-31T06:58:20Z")
Though support may be coming - > > > We currently use seconds since epoch to store dates in Elasticsearch. However, t…his is interpreted as milliseconds since epoch and stores them internally as such. > > Example: 10/Feb/2015:17:54:07 in seconds (1423590847) becomes 01/17/1970 11:26:30 > > Unfortunately this issue means that we have to use date histogram facets instead of aggregations in order to use the "factor" field to convert it accordingly (discussed in #6490). > > Possible solutions would be: mention that Unix time in seconds isn't a supported date format in the documentation or allow the Unix seconds format to be specified in the mapping. On 30 March 2015 at 09:16, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) wrote: > I thought I might have missed something, and it surprises me that the Unix > epoch isn't supported! > > Well, I guess I'll have to work around that. Thanks! > > JM > > On Sun, Mar 29, 2015 at 10:21 PM, Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com) > wrote: > > > Unix epoch isn't a supported format. Take a look at > > [format | Elasticsearch Guide [8.11] | Elastic](http://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-date-format.html) > > > > On 30 March 2015 at 02:12, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) wrote: > > > > > Here is a curl recreation, hopefully that will be clearer: > > > [#!/bin/bashset -xcurl -X DELETE 'http://localhost:9200/test-foo?pretty' - Pastebin.com](http://pastebin.com/DUhbpgze) > > > > > > JM > > > > > > On Sun, Mar 29, 2015 at 4:18 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) > > > wrote: > > > > > > > Of course I left a typo in my email: I do use the same field name > > > > across mapping def, docs and queries, and it does not work. > > > > > > > > JM > > > > > > > > On Sun, Mar 29, 2015 at 4:17 PM, Jean Marc Saffroy [jm@scality.com](mailto:jm@scality.com) > > > > wrote: > > > > > > > > > Hi all, > > > > > > > > > > Not sure what I'm doing wrong, but I couldn't find a way to store my > > > > > docs with timestamps as seconds since the Unix epoch and query them > > > > > properly. I have my date/time field mapped like this: > > > > > > > > > > "start\_time": {"type": "date" }, > > > > > > > > > > I store documents like this: > > > > > > > > > > { "start\_time": 1427631731, ... } > > > > > > > > > > And get no result when I do a range query like this: > > > > > > > > > > ``` > > > > > "query": { > > > > > "range": { "@timestamp": { "gte": "2015-03-29" }} > > > > > } > > > > > > > > > > ``` > > > > > > > > > > I have good results when I store timestamps as strings in ISO format. > > > > > > > > > > Is that supposed to work? Is there a specific date parser I should use? > > > > > > > > > > JM > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP\_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com) > > > [https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP\_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CALZqptb5xZNgok4hiszEF9JP_KRuk6y%3DwdqfbjR0xxBesK4dBA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU\_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU\_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-v%3DM6ZVK1p%3Desb40QU_Va5beBpCVusGpKeoDpcht9c2Q%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CALZqptbGPcQDxUaFHfRfttdGyzFKVUogZEenj3nAPxOJYWitCw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALZqptbGPcQDxUaFHfRfttdGyzFKVUogZEenj3nAPxOJYWitCw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CALZqptbGPcQDxUaFHfRfttdGyzFKVUogZEenj3nAPxOJYWitCw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CALZqptbGPcQDxUaFHfRfttdGyzFKVUogZEenj3nAPxOJYWitCw%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X882n7C8-C5T8DQOgqf36PG%3D6ZaJaQ6%3DxWFGVEOVmK%3DvQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X882n7C8-C5T8DQOgqf36PG%3D6ZaJaQ6%3DxWFGVEOVmK%3DvQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:22am UTC](https://discuss.elastic.co/t/timestamps-stored-as-seconds-since-unix-epoch/22971/7 "2017-07-06T00:22:55Z")