# Timestamp not as expected in kibana

**URL:** <https://discuss.elastic.co/t/timestamp-not-as-expected-in-kibana/225637>\
**Category:** Kibana\
**Created:** [March 30, 2020, 9:16am UTC](https://discuss.elastic.co/t/timestamp-not-as-expected-in-kibana/225637 "2020-03-30T09:16:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexandros888](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alexandros888](https://discuss.elastic.co/u/Alexandros888)\
**Post date:** [March 30, 2020, 9:16am UTC](https://discuss.elastic.co/t/timestamp-not-as-expected-in-kibana/225637/1 "2020-03-30T09:16:37Z")

</div>

Hello

I would like to see the indexed @timestamp value as i correctly see it in the kibana graph.

So i woud like to see 7:30:29:772 instead of 4:30:29:772.

As it can be seen from the image i am loosing 1+2=3 hours totally.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/3/23ceed65ba34d21657e3a2046c7c748fda237827.png)

While epoch converter for the specific value provides the following info:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/3/138243d819ce040fce5333a1ee408c8db18b7d33.png)

The timestamp pattern in my gelflogger appender is the following:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/b/2b9a3cba8227588035c88acd6e80e8447aa2b7ec.jpeg)

and my kibana date and time settings are as below:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/0/a0e48aaae8c08d7f1856497233ea5eac60c44c36.png)

What am i doing wrong?

---

<div class="post-metadata">

**Author:** ![Alexandros888](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alexandros888](https://discuss.elastic.co/u/Alexandros888)\
**Post date:** [March 30, 2020, 2:15pm UTC](https://discuss.elastic.co/t/timestamp-not-as-expected-in-kibana/225637/2 "2020-03-30T14:15:58Z")

</div>

In order to provide more info about the issue i use kibana verion 7.6.

If we change the value of the image bellow to the hour of our country (Greece or Switzerland for example ) problem is solved. Nevertheless, the browser option should work for each country as well.  
That leads to the conclusion that something is not ok with the kibana browser setting since it can not take the browser time setting. How can we solve that so it works with the browser setting correctly?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/b/3bb660a4e8ba3fce504791320ce4f104b786da33.png)

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [March 30, 2020, 2:35pm UTC](https://discuss.elastic.co/t/timestamp-not-as-expected-in-kibana/225637/3 "2020-03-30T14:35:05Z")

</div>

Which version are you running specifically? In `7.6.0` there is a bug which causes Kibana to run in UTC when using the "Browser" timezone - it is fixed in `7.6.1`: [https://github.com/elastic/kibana/issues/57457](https://github.com/elastic/kibana/issues/57457)

---

<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:** [April 27, 2020, 2:35pm UTC](https://discuss.elastic.co/t/timestamp-not-as-expected-in-kibana/225637/4 "2020-04-27T14:35:07Z")

</div>

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