I DO NOT WANT THAT, I don't want kibana to modify the time field, to avoid that I can set the timezone in the settings to UTC but if I do that the "now" value is equal to the UTC time (10h) and not the time from my timezone (Europe/Brussels) (12h) So i must modify the time range and add 2 hours it's horrible.
If i modify the time range by adding two hours and settings the tz in kibana to UTC (which is not but no other way to avoid the modification of the time field xd) it's good i have the current log with their valid time :
In short, the Time Zone setting for Kibana is Universal for All Date Fields in Kibana so in your Case the Time Zone picker can not be in local time and the times displayed in Discover can not then be in UTC.
BUT
There is a pretty quick way you can see both assuming you are on a fairly recent version of Elastic / Kibana. What Version are you on?
In short, Leave Kibana in Browser Zone and you can add a runtime field that will always show the UTC Time as a string and it will be available in Discover as a string, would that help?
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.