While there’re multiple tools available for monitoring, ranging from Dan Bernshtein’s daemontools to God, I found that Monit is a pretty balanced solution. On one hand, it’s quite powerful, and on the other – it’s not resource hungry. The only drawback that I found, is that for monitoring a process, the process must have a pid-file saved somewhere. The Monit FAQ states that the programs which don’t have pid-file support should be run with some wrapper which will create it on their behalf.
I wanted to use Monit to monitor Rails’ instances, so if they grow too fat, Monit will take care of that. The problem is that the pid file that the Passenger creates a) doesn’t have a predictable location (there’s something called “generation” or something like that), and b) doesn’t have children, as those processes are detached.
Of course there exists a possibility of patching Passenger for providing such pid files. But, luckily, Passenger provides extension points in form of callbacks which are fired when the application instance is created and when it’s taken down.
It was trivial to use this API to provide pid-file managing. The result of this work was the “passenger_monit” plugin.
So, go ahead, add ‘gem “passenger_monit”‘ to your Gemfile and give it a try!
The source is available from: