Global timezone support

[rashidkpc]

Timezones should be supported for all displayed date fields and all inputs that would produce a date object.

Updated this to be only a request for global timezone support. Since we use moment everywhere now this really shouldn't be too bad.

[wolfgang-werner]

I would love to analyze my data with kibana, however, my dates are all formated as basic-date-time like:

"importDate": {
"norms" : { "enabled" : false },
"type": "date",
"format": "basic_date_time",
"index": "analyzed"
}

This gives an error when selecting the field as the time field name, can not be read in Discover and results in failure when querying.

Can I configure the format to use?
+1

[marktheunissen]

Hi there, I'd just like it to be all UTC, really, and not just assume that I want to use my browser's timezone. It's mostly the datepicker that's the problem.

[drax68]

+1 here, Timezone support is highly appreciated. Any progress on this?

[stp72]

+1 here, this is a must for us!

[frexy1989]

Actually it is possible to display your own time zone at your timestamp in your table. On the left side of the table in Kibana, the field stated in my field list is Date with a capital D. So basically i go to configure on my table,go to panel tab, tick on local time and then change the time field to Date.

So i conclude that u will need to change your time field according to what is stated in ur field list. I hope this is the same problem some people is facing as me. :)

[cihadoge]

+1

[elasticdarwin]

Very appreciated.
We still need date histogram aggregating by localtime.

[haandol]

+1

[chevin99]

+1

[aabajian]

+1

[ignaciovazquez]

+1

[MichaelRuhwedel]

+1

[w33ble]

Having just run in to this issue myself, a HUGE +1 on this.

My thinking is that this should be an option in settings - you can either let it stay as it is by leaving it alone, or you could go in and manually pick the timezone you want the data to be represented in (likely with a quick "use UTC" button).

For reference, my data set had no time, just dates, so it gets saved in ES as midnight UTC. When viewing it in Kibana (from MST timezone), all my data was offset by -7 hours, so the dates were all off by 1 day.

[szsiddiq]

+1 Is there a work around out there?

[postmart]

+1 Also need to adjust timezones. please advice if there is a workaround

[jettro]

Not completely sure, but I think this is the same problem that I am facing with daylight savings on the data. Doing monthly date_histogram and get strange aggregations for the months around daylight savings. Would be nice to be able to switch it off.

[PHPSoft]

+1

[ybroze]

+1 here as well; this would be a killer feature.

[ayigal]

+1 here as well. This is absolutely critical for team that share the same Kibana but reside in different timezones.

[briw]

+1. We do everything in UTC and have ops staff across different geographic regions, a necessity to set a UTC flag on all of the graphs.

[yyoyo]

+1

[aochsner]

Is anyone working this as opposed to +1'ing it? I took a look (and I'm about the farthest thing from a front end/node/angular guru). Seems this is what moment-timezone is for. Probably should update it to 0.3.0. Add a setting. Then call moment.tz.setDefault(setting) somewhere (I'm not sure where, but when I was testing locally, I put it in discover.js but I'm sure that's the wrong place (I was only playing w/ the Discover tab).

I mean am I anywhere close here? https://github.com/aochsner/kibana/tree/issue/1600

[helkhalfi]

+1 ^_^

[roman-parkhunovskyi]

+1 is a must!

[igorgatis]

+1

[aochsner]

👏

[MirkoTV]

Hi everybody, I am seeing some unexpected behavior when I configure my kibana to work in UTC:

I think datepicker is not using moment js. I am -04:00 timezone, and notice that when I specify an hour from 0-4 am in the "from textbox" date-picker place the selected date one day before, like if it were still working with browser's timezone. Does anybody could check if this is a real bug? I would really appreciate any help. Something pretty similar happens in the other way (updating "from textbox" by modifying datepicker )

[w33ble]

Note that the above issue is being tracked in #5370. Thanks @MirkoTV

[carlosvega]

+1

[AnishShah]

+1

[wale-o]

+1

[nikkelj]

+1, I should not have to be forced to adjust my OS time zone setting to adjust what time zone I want to view my data in. Need a knob in the config.

[chrisdrusso]

+1

[jpjp]

I have users who are permanently confused by the times not matching up with the UTC server times. This feature would save this headache.

[vinuja]

+1

[tedder]

Please don't '+1'. You can use the 'reaction' emoji on the original post, and you can hit the "subscribe" button. Spamming the ~100 participants for no legit reason is just a selfish act.

[goya]

+1

[dev2see]

+1

[andris]

+1

[shubhambits]

found a fix... try changing the default.js file. In that change dateFormat:tz value to UTC .. Try this and see if it works..

edit: file is located in src/ui/settings/defaults.js

[arturo-julca]

go to settings/advanced/dateFormat:tz
done!

[shubhambits]

found this just today... forgot to post here.. anyway thanks!!

[xycloud]

any update?

[nikkelj]

Confirming the new management setting works, thanks devs!

…

On Tue, Feb 14, 2017 at 8:29 PM, xycloud ***@***.***> wrote: any update? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1600 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFhQYRbPLUr47P95p5ht76SL4sgn4ZQnks5rcnEBgaJpZM4Csk6r> .

-- Jonathan Nikkel Mobile: 303-519-4627 Work: 303-684-1706 Home: 303-502-5508 Email: nikkelj@gmail.com

[matthewkrieger]

@jordan-thoms - << This is really crazy - All that's really needed is a setting somewhere to not look at the browser timezone and just use UTC, like all our other views of our data. >> That exists today. Go to Management, Advanced Settings, type "tz" in the search box, and change the entry to "UTC".

[piotr-sokolowski]

+1

[Plasma]

Wish this was a per-user setting, we have multiple users of Kibana who have different preferences.