echo "Building a Self-Healing Network" | sed s/Network/Infrastructure/
O'Reilly has an interresting article on ONLamp.com -- Building a Self-Healing Network The idea is great however with this approach you might endup restarting apache a zillion times while not looking at the real problem.
The question is .. why did apache crash and how do we fix the problem.
We should looking to fixing the cause of the problem rather than the symptons.
Now here's off course where you have CFengine also monitor e.g your diskspace and write a nice tidy section in your cfengine configs.
However .. not all crashes are due to flooding disks so there is some other stuff you might want to investigate. I can imagine that with an editfiles section containnig RunScriptIfLineMactching you can probably fix a lot .. or at least fix issue by issue , Fix it once and forever and make that fix reproducable. Untill you run into the next undocumented problem :)