[chef] Re: Re: Re: Re: Changes to munin-recipe

[Tim Smith < >]

I would highly suggest using an attribute that default to the old method.
That's what I added in the Nagios cookbook with the multi_environment
monitoring concept.  If the user wants to grab clients from all
environment they can simple set the attribute to true.

if node['nagios']['multi_environment_monitoring']
  nodes = search(:node, "hostname:[* TO *]")
else
  nodes = search(:node, "hostname:[* TO *] AND
chef_environment:#{node.chef_environment}")
end


 
  




On 12/18/12 9:20 AM, "Andrea Campi" 
<
 >
 wrote:

>It would be nice to handle this in a similar way to the nagios cookbook;
>the latest releases have added both a multi_environment config as well as
>a data bag for arbitrary hosts not in chef (IIRC).
>
>On Dec 18, 2012, at 6:04 PM, Arnold Krille 
><
 >
> wrote:
>
>> On Tuesday 18 December 2012 14:25:26 Mat Davies wrote:
>>> Just to say thanks for this patch I also end up having to support this
>>>type
>>> of environment but didn't have time to do it properly so only hacked
>>>the
>>> templates to include the existing non-chef munin servers this is much
>>>nicer.
>> 
>> I also need this for the munin-clients at the customers location which
>>should 
>> also accept connections from our main-munin-server.
>> 
>> The patch extending munin::server to check extra_environments is
>>planned 
>> next;-) once I switched the main munin-server to chef.
>> 
>> Have fun,
>> 
>> Arnold