[chef] Re: Re: How to monitor if chef-client is actually working

[KC Braunschweig < >]

It'd be awesome if people shared their custom report/exception
handlers for tying into common monitoring/alerting tools like nagios,
zenoss etc. This is something I haven't looked at yet but will need to
get sorted before we go to prod. However, I also intend to get all
chef logging flowing through syslog and into Splunk so we can do
additional processing and alerting based on parsing the logs. Adam
already published a handler for splunk to help make this easier though
I don't know if much has been done with it besides the basic stubbing
out. I think there was also a stub for a Splunk app designed for chef
logs. Haven't played with either yet, but both are on the short term
roadmap for me.

KC

On Wed, Jun 29, 2011 at 4:31 PM, Michael Herman 
<
 >
 wrote:
> Robert,
> You can use an Exception and Report handlers to perform arbitrary code on a
> successful or failed chef-client run.
> http://wiki.opscode.com/display/chef/Exception+and+Report+Handlers
> We use a report handler, so that nagios will alarm if a successful run
> hasn't completed in the last 60 minutes or so.
> Rgds,
> mgh
>
> On Thu, Jun 30, 2011 at 9:24 AM, Robert Keng 
> <
 >
>  wrote:
>>
>> Hi all,
>> Just wondering if anyone knows if there is a way to monitor chef-client to
>> make sure it isn't stuck in retries because of some error in some recipe?
>> Does the client actually reply back to the chef-server if its able to apply
>> all recipes and things are happy?
>> I apologize if this is a really simple question, fairly new to chef...Just
>> I'd rather not have to parse /var/log/chef/client.log for this, thanks!
>> -Robert
>