Duration off by timezone offset

[jan-kantert]

With 3.13-20231208 we see an offset of 1h (our current UTC offset) in duration of alerts in Nagstamon. Not sure if this is fixed in 1429261. If it should be fixed can we get a release?

[HenriWahl]

Hi @jan-kantert, what exactly does it mean? Where the difference is effective? With which monitoring server type?

[jan-kantert]

We use Icinga2 with IcingaDB 2.14. Practically, when a check has been in critical state for 5 minutes it will be shown as 1h5m im Nagstamon. This looks like a datetime pitfall as the icinga UTC date seems to be correct (see: https://dev.arie.bovenberg.net/blog/python-datetime-pitfalls/).

[HenriWahl]

@DeadHunter @Tontonitch any idea?

[Tontonitch]

@jan-kantert could you try the latest version [Nagstamon-3.13-20240221] ?
It might be that the fix for the timezone was not in place in previous versions.

[jan-kantert]

I retested. It is fixed in master and Nagstamon-3.13-20240221. Thanks guys!