Thanks for your answer, that’s exactly the problem i have, the NTP service synchronization is working fine on all the machines with the same WARN/CRIT threshold expect 2 or 3 machines that i should synchronize them manually by running the check_mk_agent command after that they go critical when the condition is fulfilled until i run the check_mk_agent command again (manually).
note that the output of chronyc tracking looks okay:
chronyc tracking
Reference ID : B978160C (ntp01.fra-pool.fastether.net)
Stratum : 3
Ref time (UTC) : Tue Mar 22 21:34:33 2022
System time : 0.000037320 seconds fast of NTP time
Last offset : -0.000014906 seconds
RMS offset : 0.000113510 seconds
Frequency : 32.930 ppm slow
Residual freq : -0.000 ppm
Skew : 0.065 ppm
Root delay : 0.014482673 seconds
Root dispersion : 0.001599295 seconds
Update interval : 260.8 seconds
Leap status : Normal