Yes! I just looked into it and the log itself was still 2022:
2022-12-31 23:16:54.013
And then our UI converted this entry into one with 2023
(it correctly assumes that the string is in UTC and then converted it to local time +1h)
2022-12-31 23:16:54.013
And then our UI converted this entry into one with 2023
(it correctly assumes that the string is in UTC and then converted it to local time +1h)
This only happened shortly after midnight on January 1st. So I guess this is somehow related to different time zones/offsets.