# Can Kibana read timestamp field saved as millis?

**URL:** <https://discuss.elastic.co/t/can-kibana-read-timestamp-field-saved-as-millis/143070>\
**Category:** Kibana\
**Created:** [August 5, 2018, 6:39pm UTC](https://discuss.elastic.co/t/can-kibana-read-timestamp-field-saved-as-millis/143070 "2018-08-05T18:39:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anna10](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@anna10](https://discuss.elastic.co/u/anna10)\
**Post date:** [August 5, 2018, 6:39pm UTC](https://discuss.elastic.co/t/can-kibana-read-timestamp-field-saved-as-millis/143070/1 "2018-08-05T18:39:06Z")

</div>

My documents stored in ElasticSearch have a "timestamp" field that is stored as a millis ([https://currentmillis.com/](https://currentmillis.com/)) number. I would like to view time-series data in Kibana, but Timelion doesn't work properly, presumably because my @timestamp field is in a format it cannot read.

 ![timelion](https://us1.discourse-cdn.com/elastic/original/3X/7/f/7f51384f93de923f4a94df6adf44fec1dfa33058.PNG)

Is there any way I can configure Kibana to use my @timestamp field as millis, or do I need to convert the data to a certain format before sending it to ElasticSearch?

---

<div class="post-metadata">

**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\
**Post date:** [August 6, 2018, 4:36am UTC](https://discuss.elastic.co/t/can-kibana-read-timestamp-field-saved-as-millis/143070/2 "2018-08-06T04:36:02Z")

</div>

Hi Anna,

When you created the index pattern, what did you select as your time field?

Did you explicitly use some ETL to assign the timestamp to the @timestamp field? Because, by default, Elasticsearch will use the document indexing time as the @timestamp for that doc.

Also, have a look at configuring the date datatype for the index pattern using mappings:  
[https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html)

---

<div class="post-metadata">

**Author:** ![anna10](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@anna10](https://discuss.elastic.co/u/anna10)\
**Post date:** [August 7, 2018, 2:18pm UTC](https://discuss.elastic.co/t/can-kibana-read-timestamp-field-saved-as-millis/143070/3 "2018-08-07T14:18:18Z")

</div>

Thanks for the reply!

I didn't choose a time field when creating the index in ElasticSearch or Kibana.

I don't want Kibana to use the document indexing time as the timestamp, how can I configure Kibana to select the "timestamp" field from my documents as the @timestamp?

Edit: I went to try and create a new index pattern in Kibana, but when I was prompted to choose a time filter, there were no time fields found in the index.

 ![timefilter](https://us1.discourse-cdn.com/elastic/original/3X/f/2/f24461ee13355122f88058faeae8cc2569921c3d.PNG)

I realize upon reading documentation that I should have set the 'timestamp' field to '@timestamp'.

However, my index has been being populated for a few weeks now, is there a way that I can configure Kibana to interpret my 'timestamp' field as the Time Filter? Or if I configure the date datatype for the index pattern using mappings as you linked above, will this work backwards on documents that have already been indexed?

---

<div class="post-metadata">

**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\
**Post date:** [August 8, 2018, 6:14am UTC](https://discuss.elastic.co/t/can-kibana-read-timestamp-field-saved-as-millis/143070/4 "2018-08-08T06:14:16Z")

</div>

It will not work for documents that are already indexed, and if you change your mapping now, you will get a mapping conflict for your index.

You can reindex your index using the reindex api. This should resolve your issue.

> [Reindex API | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html)

---

<div class="post-metadata">

**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\
**Post date:** [August 8, 2018, 6:27am UTC](https://discuss.elastic.co/t/can-kibana-read-timestamp-field-saved-as-millis/143070/5 "2018-08-08T06:27:28Z")

</div>

Also, you do not need to rename your timestamp field. It is ok to have a field with a different name, if it is detected as a date field, the field will be visible in Kibana.

---

<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:** [September 5, 2018, 6:27am UTC](https://discuss.elastic.co/t/can-kibana-read-timestamp-field-saved-as-millis/143070/6 "2018-09-05T06:27:32Z")

</div>

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