Hello Luca,
unfortunatly, my way does not collect the start/stop messages with
monit. The status information are collected only.
hi Lutz, a good workaround, it gathers messages regarding the status,
but my aim was collecting messages/status of the actual execution of
start/stop program, although similar the flow could not be the same.
But it is a nice idea to collect the output from the last command in
monit, you should describe your problem and add an issue via Bitbucket.
Proposals or enhancement requests are welcome too, in general. And if
these information became available via M/Monit (or the web interface)
your suggestion saves some time to find problems, I think.
I use an additional file check to find useful messages, but the used
scripts write all the output to a log file too, also it is not a problem
for me and the monitored applications.
But I use the status output (from check program) to get some more
information about the application status for some applications.
With regards,
Lutz
p.s.
This is my way to handle more complex application, see
https://mmonit.com/wiki/Monit/HowTo
for example https://mmonit.com/wiki/Monit/LibertyProfileApplicationServer