Sync peer check should have a configurable grace period about ntpmon HOT 2 CLOSED

Hi Drew, somehow I only just saw this - not sure what happened there. An appropriately-configured chrony shouldn't spend much time at all selecting a new sync peer if one goes away (I would have expected a few seconds more than a few minutes). I'd be interested to see some example logs which show that behaviour.

from ntpmon.

I've discussed this with a couple other folks familiar with this problem (or similar ones), and I'm not prepared to add statefulness to the Nagios check at the moment. The recommended solution for this is to use the telegraf version of NTPmon, scrape the telegraf agent with prometheus, and use prometheus alerter to define the desired thresholds and grace periods.

from ntpmon.