- From: Daniel Schauenberg <
>
- To:
- Subject: [chef] Re: Monitoring knife-lastrun?
- Date: Sat, 9 Jun 2012 12:50:09 -0400
Hi,
wouldn't report and exception handlers be the better choice here? Sounds like
using knife lastrun is just adding complexity?
Cheers,
Daniel
On Jun 9, 2012, at 12:45 PM, Tetsu Soh wrote:
>
Hi,
>
>
May be different from what you are asking, we are using Grill to monitor
>
Chef run status.
>
It has a good GUI with alter and report feature and very easy to setup.
>
>
You can get a trial version to try Grill out.
>
>
Regards,
>
>
Tetsu
>
>
>
On 6/10/12 1:17 AM, Steffen Gebert wrote:
>
> Hi,
>
>
>
> I want to monitor the output of knife-lastrun (to check execution time +
>
> failed runs).
>
>
>
> Is anyone of you already doing this (we're using Zabbix, but I would say
>
> this fact doesn't matter..).
>
>
>
> Do you see any other way than:
>
> *) give the client on our monitoring station chef admin privileges to
>
> retrieve the values via knife (<- bad idea..)
>
> *) modify the knife-lastrun gem to write stats into a local file (however
>
> I have no clue, how to do this - I'm not a ruby guy :().
>
> *) or does knife-lastrun already write stats to a local file? However the
>
> code looks like it only writes to log and saves to the node.
>
>
>
> Would be nice, if someone could help me!
>
>
>
> Yours
>
> Steffen
>
>
Archive powered by MHonArc 2.6.16.