Handling Time Zones and Daylight saving time

[Paulo_Henrique_PH]

Hi guys,

I've got a user case where a customer is struggling to get the right aggregations due to the Daylight saving time.

We are applying the offset factor (eg -01:00) and seems like it isn't enough.

I've read a topic here (below) which states that, in order to get it right, I gotta provide the ID (e.g. "US/Central") .

Handling 1d date_histogram queries that span Daylight Saving Time (Nov 6th 2 am)

I store all my documents with date/times in GMT. Then at query time I use the "time_zone" property of a date_histogram to choose which timezone to localize it to (we have users in multiple time zones). This works great; however, I have ran into a problem for queries that span the daylight saving time change on Nov 6th and use 1d intervals. The problem arises because on Nov 6 at 2am the timezone offset changes e.g. on Nov 6th at 1 am the US Central timezone is GMT-0500, at Nov 6th at 2am the US…

Is it true?

[yeppers (Michael Parmeley)]

Yes, using the raw offset of -01:00 will not take daylight savings time into account if your query spans a daylight savings time change. Instead pass in a timezone ID. Using a timezone ID like "US/Central", "Australia/Sydney", etc makes ES aware of daylight savings time even if the change happens during the span of your query.

When I was using a -0500 offset and doing a query that spanned the fall daylight savings time change with 1h intervals I was getting one additional bucket. Changing to US/Central gave me the expected number of buckets.

[Paulo_Henrique_PH]

Thanks @yeppers