# Kibana changes timezone from UTC to CST when exporting to CSV

**URL:** <https://discuss.elastic.co/t/kibana-changes-timezone-from-utc-to-cst-when-exporting-to-csv/165491>\
**Category:** Kibana\
**Tags:** elastic-stack-reporting\
**Created:** [January 23, 2019, 10:17pm UTC](https://discuss.elastic.co/t/kibana-changes-timezone-from-utc-to-cst-when-exporting-to-csv/165491 "2019-01-23T22:17:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![slm](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@slm](https://discuss.elastic.co/u/slm)\
**Post date:** [January 23, 2019, 10:17pm UTC](https://discuss.elastic.co/t/kibana-changes-timezone-from-utc-to-cst-when-exporting-to-csv/165491/1 "2019-01-23T22:17:10Z")

</div>

One of our analysts noticed that when you generate a report in Kibana (v. 6.5.4, the resulting CSV changes all timestamps to EST time rather than using the time zone configured in dateFormat:tz (currently set to UTC). I was able to reproduce this problem by creating a saved search and exporting it as a CSV. The saved report timestamps are correct and match the timestamps in the raw message, while the timestamps in the generated CSV are off by 6 hours.

Any ideas about what might be causing this?

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [January 25, 2019, 5:49pm UTC](https://discuss.elastic.co/t/kibana-changes-timezone-from-utc-to-cst-when-exporting-to-csv/165491/2 "2019-01-25T17:49:43Z")

</div>

The `@timestamp` field is by definition UTC but Kibana is supposed to adjust it to the browser's time zone.  
-Rashmi

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [January 25, 2019, 8:56pm UTC](https://discuss.elastic.co/t/kibana-changes-timezone-from-utc-to-cst-when-exporting-to-csv/165491/3 "2019-01-25T20:56:40Z")

</div>

Am checking this behavior on latest 6.6.0 and will keep you posted.

Rashmi

---

<div class="post-metadata">

**Author:** ![slm](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@slm](https://discuss.elastic.co/u/slm)\
**Post date:** [January 28, 2019, 9:28pm UTC](https://discuss.elastic.co/t/kibana-changes-timezone-from-utc-to-cst-when-exporting-to-csv/165491/4 "2019-01-28T21:28:30Z")

</div>

As it turns out, Kibana is using the OS timezone when you generate a report rather than using the timezone in advance settings. Elastic support was able to reproduce this issue and has created a bug for it.

As a work around, I set my servers timezone to UTC and rebooted Kibana.

> <https://github.com/elastic/kibana/issues/29463>

---

<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:** [February 25, 2019, 9:28pm UTC](https://discuss.elastic.co/t/kibana-changes-timezone-from-utc-to-cst-when-exporting-to-csv/165491/5 "2019-02-25T21:28:32Z")

</div>

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