Timepicker changes timezone of Custom entered range.

[daledude]

Timepicker is assuming the timezone of the Custom range I am entering is my local browser timezone and then converts it to UTC for the filter. All our data and all panels in Kibana are using UTC. This is causing confusion since we want to search a time range using the timezone that everything else is using. Unless there is an option somewhere to have the Timepicker NOT do any form of timezone conversion on the range we enter or to use UTC then this seems odd to force only the Timepicker to use local browser.

[ghost]

I also have this problem - everything is UTC except the Custom Timepicker, which is browser time. :-(

[vaughnd]

This is driving me nuts too. I also find the custom picker keeps decrementing the day as I change the custom range.

[stonith]

@rashidkpc Any suggestions for this? The timepicker is always using browser timezone whereas the histogram, table, etc panels are configurable to browser time or UTC. This is ok for users that want everything in their local timezone but for those of us who prefer everything in UTC this causes a lot of confusion for our users.

[dhawani]

I recommend you to see this #95 (comment)

[turf00]

+1 All of our graphs and logs are in UTC and we have users across the world but the date time picker is set to their client time zone.

[rashidkpc]

I've created a general timezone ticket for this here: #1600

Kibana 4 does not currently support timezones, but we plan to support them in the future.

[penguincp]

By my study, it seems TimePicker control is translating things into UTC. In my fork, I've hacked around this. And also I want to show charts not in UTC, but in the docs that they are logged in. Check this out: http://perfspy.blogspot.com/2014/11/what-time-is-it-cheap-solution-to-make.html.