since the upgrade to 2.3.0p3 we noticed that the System Time check shows incorrect output in the Service Discovery section. In the normal view “Services of Host” the offset is displayed correctly. See attached screenshots
Inside the service discovery you only see cached output. That behavior is completely normal and no problem. You can enforce to get fresh data with the “Rescan” button.
Okay, but it seems the behavior still changed a bit. Cause a rescan does not update the offset.
At least not directly. So the check is still showing critical. At least for several minutes which is causing confusion.
All hosts showing the offset delay in the Service Discovery since the upgrade. Several colleagues noticed that.