You are welcome Phil.
Hope it helps you achieve your goals.
Let me know if you get stuck.
Pete.
On 11 April 2013 18:12, Phil Cole wrote:
> Thanks Pete,
>
> I'll take a look at your module and see how things go.
>
> Phil
>
>
>
> On Thursday, April 11, 2013 12:02:14 AM UTC+1, Pete wrote:
>>
>>
Thanks Pete,
I'll take a look at your module and see how things go.
Phil
On Thursday, April 11, 2013 12:02:14 AM UTC+1, Pete wrote:
>
> Hi Phil,
>
> The monitoring module I wrote does this very well.
> It is on puppet forge if you want to have a look for some inspiration or
> install it and
Thanks Dave.
That sounds like the sort of thing that I was looking for, but wasn't sure
if/how it would work - I'll give it a go.
Phil
On Wednesday, April 10, 2013 11:45:19 PM UTC+1, Dave Nash wrote:
>
> At work we add a tag for when setting up the nagios checks in puppet
>
> tag "nagios_env:$e
Hi Phil,
The monitoring module I wrote does this very well.
It is on puppet forge if you want to have a look for some inspiration or
install it and go from there :)
http://forge.puppetlabs.com/rendhalver/monitoring
The docs are pretty comprehensive now and explain how it all works.
I basically se
At work we add a tag for when setting up the nagios checks in puppet
tag "nagios_env:$environment"
then when we realize or export the check
We link the generation to the tag
Nagios_serviceescalation <<| tag == "nagios_env:$environment" |>> {
require => Service["nagios"],
Hi,
For several years, we have @work had a puppet environment where when we add
a new host/node, some basic monitoring is fed through to a nagios server
using virtual resources and an old nagios class which either someone here
wrote themselves, or found on the internet at the time.
We are tr
