- From: Steffen Gebert <
>
- To:
- Subject: [chef] Re: Monitoring chef runs
- Date: Thu, 6 Sep 2012 02:06:08 +0200
Same here, we're logging into Zabbix:
https://github.com/StephenKing/chef-zabbix-custom-checks/blob/master/templates/default/chef-client/chef-client-handler.rb
Yours
Steffen
On Sep 6, 2012, at 2:05 AM, Steffen Gebert
<
>
wrote:
>
Same here, we're logging into Zabbix:
>
>
https://github.com/StephenKing/chef-zabbix-custom-checks/blob/master/templates/default/chef-client/chef-client-handler.rb
>
>
Yours
>
Steffen
>
>
On Sep 6, 2012, at 1:40 AM, David Petzel
>
<
>
>
wrote:
>
>
> +1 for handlers. we have an email exception handler. The handler is
>
> applied in our base role (early on), in QA and Prod environments, but
>
> disabled in other environments so we don't spam ourselves while developing
>
> and testing updates. We are still pretty early on in our implementation,
>
> but so far this has been working for us.
>
>
>
> On Wed, Sep 5, 2012 at 7:35 PM, Brian Hatfield
>
> <
>
>
> wrote:
>
> I'm not sure if it's the quickest, but we use Chef handlers:
>
> http://wiki.opscode.com/display/chef/Exception+and+Report+Handlers
>
>
>
>
>
> On Wed, Sep 5, 2012 at 7:32 PM, Paul McCallick
>
> <
>
>
> wrote:
>
> Hi all,
>
>
>
>
>
>
>
> We’re fairly new to chef and have been manually executing chef runs on one
>
> or many nodes. We just made the move to run it as a service via the
>
> chef-client cookbook.
>
>
>
>
>
>
>
> What’s the quickest way to make sure that we’re getting notified when
>
> there are problems during a chef run? What’s the best way?
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Paul
>
>
>
>
>
>
>
Archive powered by MHonArc 2.6.16.