Sorry I don't understand what you mean by DST rules, are you talking about the ELK server?
My ELK server runs on Linux and the timezone is set to Australia/Melbourne
zdump -v Australia/Melbourne | grep 2015
Australia/Melbourne Sat Apr 4 15:59:59 2015 UT = Sun Apr 5 02:59:59 2015 AEDT isdst=1 gmtoff=39600
Australia/Melbourne Sat Apr 4 16:00:00 2015 UT = Sun Apr 5 02:00:00 2015 AEST isdst=0 gmtoff=36000
Australia/Melbourne Sat Oct 3 15:59:59 2015 UT = Sun Oct 4 01:59:59 2015 AEST isdst=0 gmtoff=36000
Australia/Melbourne Sat Oct 3 16:00:00 2015 UT = Sun Oct 4 03:00:00 2015 AEDT isdst=1 gmtoff=39600
If I change the date filter timezone to +10 instead of Australia/Melbourne, it seems to be working fine but its out by an hour
logdate 2019-11-11 23:14:40
@timestamp Nov 12, 2019 @ 00:14:40.000
EDIT: temporary brain freeze, It should be +11
I still don't understand why the original timezone doesn't work
No, it is not an ELK thing. DST is about the time suddenly jumping from 2:00 to 3:00 (meaning 2:59 does not exist) once in spring and then backwards in the autumn (so 2:01 happens twice, an hour apart). Right now I just feel too lazy to work out if clocks go back or forward in the Southern hemisphere in the Autumn.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.