# @timestamp field not identified **URL:** \ **Category:** Elasticsearch\ **Created:** [July 25, 2017, 8:28am UTC](https://discuss.elastic.co/t/timestamp-field-not-identified/94443 "2017-07-25T08:28:15Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![sLuvpreet33](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sluvpreet33/32/50626_2.png) [@sLuvpreet33](https://discuss.elastic.co/u/sLuvpreet33)\ **Post date:** [July 25, 2017, 8:28am UTC](https://discuss.elastic.co/t/timestamp-field-not-identified/94443/1 "2017-07-25T08:28:15Z")
I am pushing some old logs to elasticsearch via rsyslog. Here is one of the log entries, ``` [START] --- [xx.xx.xx.xx] --- [25/Jun/2017:06:39:54 +0530] --- "Headers: [-, -, -, -, -, -]" --- "POST /infotrack HTTP/1.1" --- 200 --- 0.310 --- "-" --- "Java/1.8.0_121" --- "application/x-www-form-urlencoded" --- "-" --- [END] ``` The logs are successfully inside the elasticsearch and visible in kibana. But the @timestamp is not identified. During adding index in kibana, the time field does not shows up. ![](https://us1.discourse-cdn.com/elastic/original/3X/0/4/047236527a0a0fdd5d0869e80077ef070eebf074.jpg) What is the problem here ? I have used the same format timestamp in other indices and it did not create any problem there. EDIT - Now I am getting this on that index, **Discover: Fielddata is disabled on text fields by default. Set fielddata=true on [@timestamp] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory.** ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 22, 2017, 8:28am UTC](https://discuss.elastic.co/t/timestamp-field-not-identified/94443/2 "2017-08-22T08:28:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.