[chef] Re: Re: Knife monitoring

[Gregory Patmore < >]

Thanks Julian, 

This is more in line with what I'm after. Tracking changes in 4 different 
environments with up to 20 knife-ers across 3 other teams besides my own is 
getting to be a cumbersome obligation. It forces me to be somewhat inflexible 
on my production environment, and with multiple dev processes happening in 
the non prod environments it's starting to turn into the Wild Wild West. 

Luckily I caught it but almost re-introduced the heart bleed bug when an 
uninformed DBA trying to push through OpenSSL upgrades by way of a dependency 
for Postgres. 

I want to be the voice of DevOps philosophy, sourcing config management from 
all tech staff, but without strict change control and issue forensics on the 
chef side, I'm forced to either throttle back software production too much or 
become the Operations Ogre defending his bridge lol. 

Sent from my iPhone

> On May 23, 2014, at 3:00 PM, "Julian C. Dunn" 
> <
 >
>  wrote:
> 
> Check out Schuberg Phillis's chef-monitor, a way that you can tap the
> RabbitMQ bus in Chef Server to grab events of interest.
> 
> https://www.cupfighter.net/2014/02/chef-monitoring
> 
> Chef Actions (a for-pay addon to EC that we announced at ChefConf and
> that will ship soon) has a similar architecture, though, of course,
> many more features.
> 
> - Julian
> 
> On Fri, May 23, 2014 at 8:02 AM, Gregory Patmore
> <
 >
>  wrote:
>> Hey all,
>> 
>> As our chef repos grow and becomes more collaborative, a need to track 
>> activity on the chef server is rising in priority for me.
>> 
>> We've wrapped the knife util to track activity, but can't enforce that 
>> people will use the wrapped util. Is there any way anyone is doing this? 
>> I'd like to implement tracking at the chef server side. Any plugin or 
>> advice would be appreciated.
>> 
>> Gregory Patmore
> 
> 
> 
> -- 
> [ Julian C. Dunn 
> <
 >
>           * Sorry, I'm    ]
> [ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ;]
> [ gopher://sdf.org/1/users/keymaker/           * compliant!    ;]
> [ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]