# Timestamp in json logs

**URL:** <https://discuss.elastic.co/t/timestamp-in-json-logs/142438>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 31, 2018, 8:00pm UTC](https://discuss.elastic.co/t/timestamp-in-json-logs/142438 "2018-07-31T20:00:52Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![PandKing](https://avatars.discourse-cdn.com/v4/letter/p/258eb7/32.png) [@PandKing](https://discuss.elastic.co/u/PandKing)\
**Post date:** [July 31, 2018, 9:52pm UTC](https://discuss.elastic.co/t/timestamp-in-json-logs/142438/8 "2018-07-31T21:52:59Z")

</div>

Followed this thread

> [@6.0.0-rc1: json.overwrite\_keys not working with @timestamp](https://discuss.elastic.co/t/6-0-0-rc1-json-overwrite-keys-not-working-with-timestamp/105189):
>
> Hi, we are trying to forward all json messages in a log file to logstash using Filebeat, but the timestamps are already off on the Filebeat side. With 5.0.1 it is working, with 6.0.0-rc1 we get duplicate @timestamp fields. Sample JSON: { "@timestamp": "2017-10-17T10:03:14.301Z", "request": "/" } Sample Filebeat Config 5.0.1 (working): filebeat.prospectors: - input\_type: log paths: - serverlogs/apache.json json.keys\_under\_root: true json.add\_error\_key: true json.overwrite\_keys: …

---

_[View the full topic](https://discuss.elastic.co/t/timestamp-in-json-logs/142438)._