# Kibana User with diferent GMT time

**URL:** <https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917>\
**Category:** Kibana\
**Created:** [November 27, 2020, 10:04pm UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917 "2020-11-27T22:04:19Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samuel\_Amico](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samuel_amico/32/75326_2.png) [@Samuel\_Amico](https://discuss.elastic.co/u/Samuel_Amico)\
**Post date:** [November 27, 2020, 10:04pm UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/1 "2020-11-27T22:04:19Z")

</div>

Ok guys this is very IMPORTANT !!!

I have my admin Space with my elastic superuser and I put this setting:

Advance Settings -\> Timezone for date formatting = America/Belem

I the other Space (Supervisor space) that has the supervis user I put the same setting:

Advance Settings -\> Timezone for date formatting = America/Belem

However, when the supervis login and generate a report csv, the timestamp comes in with the wrong Timezone (with +GMT 3). How can I fix that ?

---

<div class="post-metadata">

**Author:** ![clintandrewhall](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clintandrewhall/32/45435_2.png) [@clintandrewhall](https://discuss.elastic.co/u/clintandrewhall)\
**Post date:** [November 27, 2020, 10:46pm UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/2 "2020-11-27T22:46:42Z")

</div>

Can you confirm your Kibana version, and from where you're generating the report? Searching through the forum and GitHub, I found a lot of (fixed) older reports of this issue:

> <https://github.com/elastic/kibana/issues/31131>
>
> Kibana version: 6.6.1 BC1
> Elasticsearch version: 6.6.1 BC1
> Server OS version: darwin\_x86\_64
> Browser version: chrome latest
> Browser OS version: OS X
> Original install method (e.g. download...

  
[https://discuss.elastic.co/search?q=timezone%20csv%20category%3A7](https://discuss.elastic.co/search?q=timezone%20csv%20category%3A7)

---

<div class="post-metadata">

**Author:** ![Samuel\_Amico](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samuel_amico/32/75326_2.png) [@Samuel\_Amico](https://discuss.elastic.co/u/Samuel_Amico)\
**Post date:** [November 28, 2020, 12:36am UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/3 "2020-11-28T00:36:53Z")

</div>

Kibana and Elastic on the last version: 7.9.  
I generate the reporting in discovery and download to my Excel.

---

<div class="post-metadata">

**Author:** ![Samuel\_Amico](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samuel_amico/32/75326_2.png) [@Samuel\_Amico](https://discuss.elastic.co/u/Samuel_Amico)\
**Post date:** [November 28, 2020, 12:45am UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/4 "2020-11-28T00:45:06Z")

</div>

My Machine Timestamp is correct, when I download the same reporting using my admin Space its looks like the correct timestamp, but with diferent user don't. But when I put kibana\_adm Role to my user, the csv reporting look's correct. Why ?

---

<div class="post-metadata">

**Author:** ![Samuel\_Amico](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samuel_amico/32/75326_2.png) [@Samuel\_Amico](https://discuss.elastic.co/u/Samuel_Amico)\
**Post date:** [November 28, 2020, 3:12pm UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/5 "2020-11-28T15:12:24Z")

</div>

![2Capturar](https://us1.discourse-cdn.com/elastic/original/3X/e/8/e8471e13674486bea4f0a848f5d4028ade4cc2ee.png)  
In my Admin Space show the same

 ![1Capturar](https://us1.discourse-cdn.com/elastic/original/3X/2/2/22a8f3d05e26f583d6611eb9790e9baaac63ab33.png)  
In the Superv show the same Timestamp UTC  
but the reporting csv for the Superv space on User super comes with different GMT+3

---

<div class="post-metadata">

**Author:** ![Samuel\_Amico](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samuel_amico/32/75326_2.png) [@Samuel\_Amico](https://discuss.elastic.co/u/Samuel_Amico)\
**Post date:** [November 30, 2020, 11:54am UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/6 "2020-11-30T11:54:58Z")

</div>

clintandrewhall please watch the video that a I made, I reporting this issue. This is very serious, please take a very look special.

Please Watch this videos in my Github: [https://github.com/samuelamico/ElasticSearchBugs](https://github.com/samuelamico/ElasticSearchBugs)

Again:

Steps for reproduction:  
KIBANA AND ELASTIC IN 7.9

1. I have two spaces (Admin and Super), with two logins (elastic and supervisor), with the supervisor only having read access and only to the Super space, he is a dashboard end-user.
2. The reports inside DISCOVERY are downloaded in csv and for the admin user (elastic) the timestamp used comes in the timestamp format of America / Belem.
3. When the Super user accesses the same report and does the download, the timestamp in the column does not come in the America / Belem format timestamp, but in the Browser. And it was not set in the Super space as a default.
4. However, for some reason when I give kibana\_admin permission to the supervising user, I will download the report and it will come in the timestamp format America / Belem.

---

<div class="post-metadata">

**Author:** ![clintandrewhall](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clintandrewhall/32/45435_2.png) [@clintandrewhall](https://discuss.elastic.co/u/clintandrewhall)\
**Post date:** [December 1, 2020, 4:31pm UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/7 "2020-12-01T16:31:18Z")

</div>

Thank you, Samuel! I'll take a look and chat with some other folks in Kibana about what may be causing this. Stay tuned!

---

<div class="post-metadata">

**Author:** ![clintandrewhall](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clintandrewhall/32/45435_2.png) [@clintandrewhall](https://discuss.elastic.co/u/clintandrewhall)\
**Post date:** [December 1, 2020, 11:39pm UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/8 "2020-12-01T23:39:43Z")

</div>

Thank you for your patience, Samuel.

We've been discussing this, and we're going to treat it as a bug for now. I've created an issue here:

> <https://github.com/elastic/kibana/issues/84717>
>
> Kibana version:
> 7.9
> Elasticsearch version:
> Server OS version:
> Browser version:
> Browser OS version:
> Original install method (e.g. download page, yum, from source, etc.):
> Describe the bug:
> This was originally...

Please add your comments, perhaps help me "fill in the blanks", so to speak, about what I may be missing. We're having a hard time reproducing it, as well. It would be helpful to know specifically how the spaces are configured, the specifics of the user roles, the index privileges, etc.

Two suggestions for a short-term mitigation were:

1. Consider upgrading, if appropriate, or at least ensure you are running 7.9.3.
2. Set the timezone to `America/Belem` for all of Kibana in your `kibana.yml`:

`uiSettings.overrides.dateFormat:tz: "America/Belem"`

Thank you for bringing this to our attention. Feel free to comment again here, but your input on the Github issue will be very valuable.

Cheers!

---

<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 29, 2020, 11:40pm UTC](https://discuss.elastic.co/t/kibana-user-with-diferent-gmt-time/256917/9 "2020-12-29T23:40:03Z")

</div>

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