invoke-icingachecktimesync not capable of handling negative values
robertkrenn opened this issue · 1 comments
robertkrenn commented
While checking the timesync on our windows servers, it happens quite often, that the timesync offset is for example -30ms. The check imediately turns critical saying "-30ms is greater than the threshold of 500ms", what is completely wrong in each way. What is the defined way to deal with that. By setting threshold to 500ms we think 500ms by value, positive and negative offset to the timeserver.
LordHepipud commented
Thank you for the issue. Please have a look on the Plugin Documentation for threshold handling.
In order to receive a CRITICAL
state only if the value exceeds 500ms, you have to modify your threshold like this:
~:500ms
If you want to check for a value lower than 500ms and higher than 500ms, it would be like this:
-500ms:500ms