# Two timezones in JSON log

**URL:** <https://discuss.elastic.co/t/two-timezones-in-json-log/116877>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 24, 2018, 2:36pm UTC](https://discuss.elastic.co/t/two-timezones-in-json-log/116877 "2018-01-24T14:36:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [January 24, 2018, 3:46pm UTC](https://discuss.elastic.co/t/two-timezones-in-json-log/116877/4 "2018-01-24T15:46:11Z")

</div>

It is not possible to modify the format or timezone used in the `@timestamp` field for Beats. It's not a practice we encourage. Why do you want to change the timezone of `@timestamp`?

This has been discussed in the context of Logstash in another post: [How to set @timestamp timezone?](https://discuss.elastic.co/t/how-to-set-timestamp-timezone/28401)

You could probably use a ruby filter to mutate the timezone in Logstash. ES will always store the value as UTC internally. [https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html)

---

_[View the full topic](https://discuss.elastic.co/t/two-timezones-in-json-log/116877)._