I’m searching for a possibility to verify the check result freshness from a master or satellite point for a client check:
I’m using the config sync method to configure my checks on the clients. Whenever the connection to a client gets lost, the master recognizes that the client’s checks are overdue, but as the check is only being performed from the client side, the master (or satellite) does not perform any freshness checks. Therefore the overdue services stall in the “OK” state (or whatever was the last successful check result) and do not turn to “CRITICAL” or “UNKNOWN”.
How to archive that checks performed from clients turn into a “UNKNOWN” state whenever the check is overdue as the client has lost its connection to the master/satellite?