# Correct @timestamp format for JSON ingress

**URL:** https://discuss.elastic.co/t/correct-timestamp-format-for-json-ingress/76653
**Category:** Beats
**Tags:** filebeat
**Created:** [February 27, 2017, 4:22pm UTC](https://discuss.elastic.co/t/correct-timestamp-format-for-json-ingress/76653 "2017-02-27T16:22:21Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Cylindric](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cylindric/32/5660_2.png) [@Cylindric](https://discuss.elastic.co/u/Cylindric)
#### Post date: [February 27, 2017, 4:22pm UTC](https://discuss.elastic.co/t/correct-timestamp-format-for-json-ingress/76653/1 "2017-02-27T16:22:21Z")

</div>

Hi. I'm using Filebeat to import data from a log file that is putting a JSON object in a log file.

I am getting parser errors on import:

```
@timestamp not overwritten (parse error on 2017-02-27T16:19:08)

```

An example of a line is:

```
{"remoteHost": "81.109.116.50","remoteUser": "-","@timestamp": "2017-02-27T16:15:38","requestMethod": "GET"}

```

What is the correct and parsable date/time format for the @timestamp?

thanks

---

_[View the full topic](https://discuss.elastic.co/t/correct-timestamp-format-for-json-ingress/76653)._