# 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:** 3
**Page:** 1
### Author:  [@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")
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
---
### Author:  [@Cylindric](https://discuss.elastic.co/u/Cylindric)
#### Post date: [March 1, 2017, 9:28am UTC](https://discuss.elastic.co/t/correct-timestamp-format-for-json-ingress/76653/2 "2017-03-01T09:28:05Z")
Turns out I was just missing the terminating `Z`, so this is what I ended up with:
```
2017-02-27T16:15:38Z
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 29, 2017, 9:28am UTC](https://discuss.elastic.co/t/correct-timestamp-format-for-json-ingress/76653/3 "2017-03-29T09:28:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.