# Timezone issue in Kibana

**URL:** <https://discuss.elastic.co/t/timezone-issue-in-kibana/221666>\
**Category:** Kibana\
**Created:** [March 2, 2020, 11:23am UTC](https://discuss.elastic.co/t/timezone-issue-in-kibana/221666 "2020-03-02T11:23:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rcganesh](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rcganesh](https://discuss.elastic.co/u/rcganesh)\
**Post date:** [March 2, 2020, 11:23am UTC](https://discuss.elastic.co/t/timezone-issue-in-kibana/221666/1 "2020-03-02T11:23:11Z")

</div>

Hello,

We are injecting data into elasticsearch from MQs. Both the MQ and elasticsearch servers are in the same time zone (AST). However, when data is displayed in Kibana, time zone changes to _ **AST+3** _ hours.

For instance, the timestamp in the current date is  
`// 2020-03-02T12:36:03.816`

But when we see it in Kibana, it shows,  
`// 2020-03-02T15:36:03.816`

I do understand, there is an option to change Timezone in Kiban through "Advance Settings". Although, making changes in "Advance Settings" of Kibana helps to show the data as per the required time zone, but it fails when we want to set alert because "now" and the current timestamp has a difference of 3 hours.

Any help or suggestion is really appreciated.

Thank you.

Ravi.

---

<div class="post-metadata">

**Author:** ![Magnus\_Kessler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnus_kessler/32/42001_2.png) [@Magnus\_Kessler](https://discuss.elastic.co/u/Magnus_Kessler)\
**Post date:** [March 2, 2020, 1:59pm UTC](https://discuss.elastic.co/t/timezone-issue-in-kibana/221666/2 "2020-03-02T13:59:45Z")

</div>

When used without timezone information, Elasticsearch interprets dates as being in UTC. Internally, dates are always converted to the milliseconds since the epoch in UTC. Kibana converts this to the local timezone that the browser uses.

If possible in your application, try sending the original time stamps with a timezone, e.g. `2020-03-02T12:36:03.816+03:00`. If the format cannot be changed before being sent to Elasticsearch, it can be fixed-up in e.g. an ingest pipeline. The [date processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/date-processor.html) can use an optional timezone parameter.

---

<div class="post-metadata">

**Author:** ![rcganesh](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rcganesh](https://discuss.elastic.co/u/rcganesh)\
**Post date:** [March 29, 2020, 11:12am UTC](https://discuss.elastic.co/t/timezone-issue-in-kibana/221666/3 "2020-03-29T11:12:23Z")

</div>

Thank you Magnus.

Your suggestion really helped.

---

<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 26, 2020, 11:12am UTC](https://discuss.elastic.co/t/timezone-issue-in-kibana/221666/4 "2020-04-26T11:12:24Z")

</div>

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