# Logstash Json filter re-formated the @timestamp field unexpectedly

**URL:** <https://discuss.elastic.co/t/logstash-json-filter-re-formated-the-timestamp-field-unexpectedly/237027>\
**Category:** Logstash\
**Created:** [June 14, 2020, 4:35pm UTC](https://discuss.elastic.co/t/logstash-json-filter-re-formated-the-timestamp-field-unexpectedly/237027 "2020-06-14T16:35:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [June 14, 2020, 5:20pm UTC](https://discuss.elastic.co/t/logstash-json-filter-re-formated-the-timestamp-field-unexpectedly/237027/4 "2020-06-14T17:20:37Z")

</div>

Support for epoch values when coercing @timestamp is discussed [here](https://github.com/elastic/logstash/pull/10369).

Moving values from a field to the root level is pretty cheap. The ruby code is [here](https://discuss.elastic.co/t/how-to-dynamically-move-nested-key-value-to-root-level/180006/2).

---

_[View the full topic](https://discuss.elastic.co/t/logstash-json-filter-re-formated-the-timestamp-field-unexpectedly/237027)._