apsoto/monit — pull request #30 by anujbiyani (2013-05-21 00:06:53+00:00)
Title: Add recipes for monitoring resque workers and a scheduler

Based on what you said [here](https://github.com/apsoto/monit/pull/19) it sounds like adding recipes for monitoring specific packages is something you'd rather avoid, but you're open to discussing it.

I think it's a good idea to support recipes like this for a couple reasons:
1. Allows the end-user to keep their monit stuff in a monit cookbook. If I want to use the monitrc definition, I have to write a recipe in my own cookbook that calls the definition and maybe supplies a template file. Then in the future if I ever change from monit to some other monitoring service, I have to remove code from multiple locations.
2. These recipes are sometimes useful to other people. In this specific case (resque), it's not rare for a Rails app to be using resque and monit; it'd be nice to also provide them with sane defaults.
3. Reduces the number of forks so that there's one canonical repo for all things monit.

On the flip side:
1. The burden of maintaining these recipes falls on you instead of on a fork or in a private repository.
2. This cookbook could grow to be quite large if a lot of different recipes are added.