log1-c

Just realised that this is only true when using the "Minimal view". With "Common view" or "Detailed view" the icons are displayed correctly.  Not sure if this was that...

Huh, it does :D don't know why I missed that until now... Though I personally would favor a "real" timestamp instead of "x minutes ago" in the output as well...

Quick question: would this also fix the following issue: Downtimes scheduled via API (sometimes) get synced/re-created with delay and are doubled #10078

Can confirm: ```powershell PS C:\Windows\system32> Set-IcingaServiceUser -User 'NT AUTHORITY\System' False PS C:\Windows\system32> Set-IcingaServiceEnvironment PS C:\Windows\system32> Set-IcingaServiceUser -User 'NT AUTHORITY\System' [Notice]: Service User "NT AUTHORITY\System" for service "icinga2" successfully updated True...

Running ```powershell Set-IcingaServiceEnvironment Set-IcingaAgentServiceUser -user 'NT Authority\SYSTEM' Restart-Service -name "icinga2" ``` does not work reliably via the script called by Ansible. Not sure why. Maybe because `Set-IcingaServiceEnvironment` takes some time...

I have tested what happens during a switch-over: Patroni node status: Leader changes to "unknown" for a short time, new leader changes from "replica" to "leader". `hot_standby` is necessary for...

Follow up to this: Due to the changes mentioned in the linked lib/pq issue the error message is now more specific: ``` Dec 17 20:18:19 msd-ic-ma02 icingadb[1674]: Starting history sync...