I am currently considering moving from Supervisor to Monit in order to monitor a Laravel queue worker. Main reason is the ability to monitor CPU, Memory, and set email alerts (afaik with Supervisor I must install another package) since I will want to monitor other things soon such as Redis and perhaps the overall stability and performance of the web server.
To my limited knowledge in process monitoring, Monit is more robust and suitable for the job.
All the documentation that I could find about Laravel and Queue/Job monitoring refer to using Supervisor and, when trying to set it up manually I got stuck with setting up the pid file for the queue listener (I am not a sysadmin).
Is there a reason for Laravel to endorse only Supervisor and not mention Monit at all? (https://laravel.com/docs/5.3/queues#queue-workers-and-deployment)
If not - can someone help with how the setup of the Monit configuration will be per a Laravel queue worker?
Assuming I have a project under /var/www/html/laravel
and I would want the process monitored to be /var/www/html/laravel/artisan queue:work --daemon
I tried following this question but without much success.