Running with monit 5.5 (but have also reproduced this behavior on monit 5.10)
Have monit configs that use every x cycles like so:
check process sensu-client with pidfile /var/run/sensu/sensu-client.pid every 10 cycles
Many support folks aren't familiar with the actual monit config files, but use the command monit status to check basic system sanity. 90% of the time they end up seeing output like so:
monitoring status Waiting
People are constantly confused as to what Waiting means when they see other processes that aren't using the every X cycles as Running. They either think the process is not running or that monit is stuck waiting for the process to start even though the process is running just fine.
And only 10% of the time do they get this output:
monitoring status Monitored
I assume it's only showing the Running state when the previous cycle was the 10th cycle when it actually check the process.
Is this by design or a bug? Could this output be improved so that it somehow indicates the status the last time monit actually checked the process?