# Timezone problem, data displayed in the future

**URL:** <https://discuss.elastic.co/t/timezone-problem-data-displayed-in-the-future/157665>\
**Category:** Kibana\
**Created:** [November 21, 2018, 9:35am UTC](https://discuss.elastic.co/t/timezone-problem-data-displayed-in-the-future/157665 "2018-11-21T09:35:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nanolike](https://avatars.discourse-cdn.com/v4/letter/n/58f4c7/32.png) [@Nanolike](https://discuss.elastic.co/u/Nanolike)\
**Post date:** [November 21, 2018, 9:35am UTC](https://discuss.elastic.co/t/timezone-problem-data-displayed-in-the-future/157665/1 "2018-11-21T09:35:38Z")

</div>

Hi !

I'm new to Kibana and I looked for an answer but found nothing although this seems to be a popular topic.

I'm in France (UTC+1) and using Filebeat.  
The problem is when a log is sent, say at 9:30 AM kibana shows it at 10:30 AM. If I check the document JSON the @timestamp is correct, but displayed differently..

Here is an example:  
 ![25](https://us1.discourse-cdn.com/elastic/original/3X/9/f/9f81bcad7ba47f8512050d6bf744836328db1d11.png)

And the raw JSON:  
 ![36](https://us1.discourse-cdn.com/elastic/original/3X/4/3/43fece039fcbe252cab98e3fc96a5f78facf7cf8.png)

Any thoughts ?

Thanks

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 21, 2018, 9:55am UTC](https://discuss.elastic.co/t/timezone-problem-data-displayed-in-the-future/157665/2 "2018-11-21T09:55:46Z")

</div>

Timestamps in Elasticsearch has to be in UTC timezone, which is why the JSON document looks the way it does. When Kibana displays data it will adjust timestamps based on the browsers timezone, which is why it differs from the raw data, which is not modified by Kibana.

---

<div class="post-metadata">

**Author:** ![Nanolike](https://avatars.discourse-cdn.com/v4/letter/n/58f4c7/32.png) [@Nanolike](https://discuss.elastic.co/u/Nanolike)\
**Post date:** [November 21, 2018, 9:58am UTC](https://discuss.elastic.co/t/timezone-problem-data-displayed-in-the-future/157665/3 "2018-11-21T09:58:09Z")

</div>

Thanks for quick answer.

Indeed the @timestamp in the JSON is not UTC but UTC+1.  
Do you know how can I change that ?

FYI heartbeat and metricbeat send correct UTC timestamp...  
I just have this problem with filebeat.

---

<div class="post-metadata">

**Author:** ![Nanolike](https://avatars.discourse-cdn.com/v4/letter/n/58f4c7/32.png) [@Nanolike](https://discuss.elastic.co/u/Nanolike)\
**Post date:** [November 22, 2018, 11:14am UTC](https://discuss.elastic.co/t/timezone-problem-data-displayed-in-the-future/157665/5 "2018-11-22T11:14:59Z")

</div>

It was a filebeat configuration problem, so it's ok now.  
Can close this topic 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 20, 2018, 11:15am UTC](https://discuss.elastic.co/t/timezone-problem-data-displayed-in-the-future/157665/6 "2018-12-20T11:15:01Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.