Does the “for cycles” option work for you? Example, “check server xxx for 10 cycles”. The cycles is the daemon interval time.
Thanks, -Ron > On Mar 13, 2025, at 12:22 AM, Steven Christensen <[email protected]> wrote: > > > Hi All, I have a use case I am not sure Monit can handle. I looked at the > document and tried keywords in this mailing list, but nothing came up. > > I have a script which checks another node for some information, and then > reports success or failure (via exit code).The script works fine in Monit. > > But due to some dodgy DNS service, sometimes when the script tries to get > information from the other node, the DNS lookup fails. So we don't know > whether the information would have resulted in a success or failure, to > report to Monit. > > My question: Is there a way to tell Monit during that script check interval > that the results of the check are indeterminate, that it should maintain the > previous success/failure state until it the next time it is able to > definitively report a true or false status? > > Thanks! >
