[chef] Re: Re: Re: Life cycle of a chef run

[Tim Uckun < >]

On Fri, Oct 23, 2009 at 6:14 AM, Daniel DeLeo 
<
 >
 wrote:
> Tim,
> One (really hacky, some might even say kludgy) way to accomplish what you
> want, at least for reporting of failed runs via email, would be to include a
> Ruby at_exit hook in a recipe.  Note that this is only effective if you run
> the client via cron or some mechanism where the chef-client program
> exits--so anything using the interval (-i) option won't work with this hack.
> Here's some code that demonstrates the various behaviors you can see with
> at_exit
>>


Thanks. That's an approach I might try.

I use zabbix for monitoring so I could also send some data to the
monitoring server from those hooks too I suppose.

In any case it might be enough (for me) to know that something went
wrong even if it means I have to log into the server and investigate
further.