[chef] Re: Life cycle of a chef run

[Nick Ohanian < >]

I second this.  I had the same need, and I ended up rolling my own scripts to do this.  Otherwise there is no 
visibility into what's "really" going on in the deployment.  However, while this is certainly an important 
part of "managing your servers", it might be outside of the scope of Chef's goals.  Chef is good at 
"configuring your servers", but is it the intent of Chef to (eventually) provide support for 
"monitoring your servers"?

-Nick


Tim Uckun wrote:
> Is there a way to wrap some code around the chef run?
>
> I have two specific goals.
>
> 1. Catch exceptions and email them to me.
> 2. Send some data to my monitoring service after the run (if nothing
> else just the fact that the run took place and went OK but I would
> like to include other data from ohai).