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.
rashidkpc
All 116 comments
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
wolfgang-werner
on 14 Oct 2014
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.
marktheunissen
on 17 Oct 2014
+1 here, Timezone support is highly appreciated. Any progress on this?
drax68
on 8 Dec 2014
+1 here, this is a must for us!
stp72
on 15 Dec 2014
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. :)
frexy1989
on 17 Dec 2014
+1
cihadoge
on 11 Jan 2015
Very appreciated.
We still need date histogram aggregating by localtime.
elasticdarwin
on 26 Jan 2015
+1
haandol
on 2 Feb 2015
+1
chevin99
on 2 Feb 2015
+1
aabajian
on 13 Feb 2015
+1
ignaciovazquez
on 17 Feb 2015
+1
MichaelRuhwedel
on 24 Feb 2015
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.
w33ble
on 26 Feb 2015
+1 Is there a work around out there?
szsiddiq
on 5 Mar 2015
+1 Also need to adjust timezones. please advice if there is a workaround
postmart
on 26 Mar 2015
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.
jettro
on 31 Mar 2015
+1
PHPSoft
on 1 Apr 2015
+1 here as well; this would be a killer feature.
ybroze
on 3 Apr 2015
+1 here as well. This is absolutely critical for team that share the same Kibana but reside in different timezones.
ayigal
on 5 Apr 2015
+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.
briw
on 6 Apr 2015
+1
yyoyo
on 7 Apr 2015
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
aochsner
on 8 Apr 2015
+1 ^_^
helkhalfi
on 16 Apr 2015
+1 is a must!
rparkhunovskyi
on 16 Apr 2015
+1 ! having a timestamp to choose in the timepicker a time different from the real time I'm searching in the dataset (in UTC) is a real pain. My cheap workaround (tested on chromium and firefox) is change the TZ env variable to UTC and the open the browser from the same terminal.
export TZ=UTC; firefox
epikt
on 17 Apr 2015
+1
JosVerburg
on 17 Apr 2015
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.
jordan-thoms
on 20 Apr 2015
+1
ESamir
on 20 Apr 2015
+1 could really use this right now! :)
rodneykeeling
on 22 Apr 2015
+1
Diastro
on 26 Apr 2015
+1
toleksyn
on 28 Apr 2015
+1, it would be awesome.
oshmyrko
on 28 Apr 2015
+1
greg82p
on 30 Apr 2015
+1
hoyeol
on 30 Apr 2015
+1
wellle
on 7 May 2015
I see a lot of closed issues for this, is there a solution to it here cause I'm not seein it
timhavens
on 7 May 2015
Working on it #3588 Just haven't had enough dedicated time to get it to done (and my front end dev skills are pretty weak..). Welcome to any help.
aochsner
on 7 May 2015
+1
petromatviichuk
on 8 May 2015
The elastic blog on Kibana 4.1 last week mentions "Added a “select" type to the advanced settings screen to support a community pull to add timezone support." But I don't see where that is - does anyone else (I am running the latest snapshot)? Screenshots would be helpful. Thanks!
szsiddiq
on 9 May 2015
I'm not sure if that's in an official release yet; might just be on master at this point in time.
rodneykeeling
on 9 May 2015
+1
lgbs
on 19 May 2015
++1
naisanza
on 21 May 2015
+++1
abdalians
on 21 May 2015
+1 a generic setting of using UTC in the settings section would be helpful.
As I understand it, the (local) timezone is currently auto added when defining the aggregations over time. It can be seen in the generated request detail. What helped me as a workaround was adding {"time_zone":0} as a json fragment into the 'advanced' box of the aggregation. That sets the timezone back to UTC and needs to be done for every visualization separately.
ThomasKunkel
on 21 May 2015
Hi +1
A workaround is to convert data when saving then to elasticsearch using the Date filter.
defus
on 25 May 2015
+1
Ginja
on 26 May 2015
+1 Much needed!
IngaFeick
on 28 May 2015
+1
mre
on 28 May 2015
+1
xo4n
on 28 May 2015
+1
MaxBosse
on 28 May 2015
+1 It will be a good feature to prioritise this as we have Analysts sitting in different timezones and we dont have to push dates in different timezones. Also I like to know how to use moment everywhere as a workaround for the time being and see if it resolves our current problem .
deepakas
on 2 Jun 2015
+1. And special thanks to ThomasKunkel for providing workaround.
yienge
on 3 Jun 2015
+1
In our observatory we share the data with people across the world. So the only meaningful time zone is UTC.
jpgil
on 6 Jun 2015
+1
I encounter this problem with the search query. the time field did not show correctly!
arganzheng
on 29 Jun 2015
+1
codebucketdev
on 2 Jul 2015
+1
gesellix
on 2 Jul 2015
+1
kongsgard
on 29 Jul 2015
+1
me0wster
on 29 Jul 2015
+1
luckychild305
on 31 Jul 2015
+1
taraslayshchuk
on 31 Jul 2015
+1
lmazuel
on 3 Aug 2015
+1
deviantony
on 4 Aug 2015
+1
inevu
on 8 Aug 2015
+1
clintfoster
on 10 Aug 2015
:+1:
vbfox
on 11 Aug 2015
+1
alexganwd
on 11 Aug 2015
+1
Maran123
on 20 Aug 2015
:+1:
pemontto
on 24 Aug 2015
+1
yoshiso
on 26 Aug 2015
Please fix this 'yo!
mblomdahl
on 2 Sep 2015
+1
frecar
on 2 Sep 2015
+1, can I vote twice?
vichargrave
on 2 Sep 2015
You can even vote 50 times – I'm not seeing votes having any impact, the feature keeps being bumped away. First birthday soon!
davux
on 3 Sep 2015
+1
hex6ng
on 4 Sep 2015
+1
yuanhang
on 8 Sep 2015
+1
xiaoping378
on 9 Sep 2015
+1, the issue is very important!
During using kibana, we found that the whole time forwards eight hours in China!!!
tangyong
on 9 Sep 2015
No love for this issue. The original issue https://github.com/elastic/kibana/issues/95 has been open since May 20, 2013.
rtkmhart
on 9 Sep 2015
+1
fandrei
on 10 Sep 2015
Not having this it's the only reason why we can't use ELK in production.
epikt
on 13 Sep 2015
Please fix this bug. Or give me a way to avoid this.
zhangzk
on 13 Sep 2015
+1
zhangzk
on 13 Sep 2015
+1 pleeeeaseee this would be really really helpful, my logstash works in one timezone and my kibana in another one, I am seeing all the information 15 hours behind!
MirkoTV
on 17 Sep 2015
+1
xo4n
on 17 Sep 2015
+1 from all of us
arun936
on 22 Sep 2015
+1
shumkov
on 25 Sep 2015
+1
goya
on 1 Oct 2015
+1
philbb
on 2 Oct 2015
+1
tonyjchong
on 6 Oct 2015
+1. Specifically, I am looking to have searches executed in the correct time-based index name (it is currently searching date based on UTC instead of desired timezone). I believe this is related.
ahartimvu
on 6 Oct 2015
+1
aidzan
on 7 Oct 2015
+1
cincauhangus
on 13 Oct 2015
Something that I would like to add here.... It would be really helpful to provide some way to support "birthday dates" or "calendar dates". Some way to prevent kibana from modifying a date based on the time zone cause my birthday or independence day is the same day anywhere and should not be modified for the timezone
MirkoTV
on 13 Oct 2015
+1
igorgatis
on 19 Oct 2015
:clap:
aochsner
on 20 Oct 2015
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 )
MirkoTV
on 11 Nov 2015
Note that the above issue is being tracked in #5370. Thanks @MirkoTV
w33ble
on 11 Nov 2015
+1
carlosvega
on 19 Nov 2015
+1
AnishShah
on 4 Dec 2015
+1
wale-o
on 31 Dec 2015
+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.
nikkelj
on 12 Jan 2016
+1
chrisdrusso
on 14 Mar 2016
I have users who are permanently confused by the times not matching up with the UTC server times. This feature would save this headache.
jpjp
on 30 Mar 2016
+1
vinuja
on 24 May 2016
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.
tedder
on 24 May 2016
+1
goya
on 24 May 2016
+1
dev2see
on 30 Jun 2016
+1
andris
on 4 Aug 2016
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
shubhambits
on 11 Aug 2016
go to settings/advanced/dateFormat:tz
done!
arturo-julca
on 11 Aug 2016
found this just today... forgot to post here.. anyway thanks!!
shubhambits
on 11 Aug 2016
any update?
xycloud
on 15 Feb 2017
Confirming the new management setting works, thanks devs!
On Tue, Feb 14, 2017 at 8:29 PM, xycloud notifications@github.com wrote:
any update?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elastic/kibana/issues/1600#issuecomment-279907526,
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: [email protected]
nikkelj
on 15 Feb 2017
@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".
matthewkrieger
on 12 Aug 2018
+1
piotr-sokolowski
on 6 Sep 2018
Wish this was a per-user setting, we have multiple users of Kibana who have different preferences.
Plasma
on 6 Apr 2020
Related issues
ctindel
·
3Comments
LukeMathWalker
·
3Comments
bradvido
·
3Comments
tbragin
·
3Comments
snide
·
3Comments
Most helpful comment
go to settings/advanced/dateFormat:tz
done!