search for: nagios_host

Hi, so I''m trying to use the built in nagios_host type and there appears to be one huge glaring hole - the lack of a hostgroups parameter. And before anyone asks why I can''t use the nagios_hostgroup type, if someone can tell me how I can collect members without having to manage the hostgroup members manually, that would be fantastic. Th...

...t I started down the road of using exported resources This was inspired by my reading all of the nagios related recipes that went something along the lines of class nagios { package {nagios: ensure=> latest } service {nagios : ensure => running , enable => true} Nagios_host <<! !>> Nagios_service <<! |> class target { @@nagios_host { $fqdn: ensure => present, alias => $hostname, register =&gt...

Hi, Since the below is a little long, I put my question at the top: how do I troubleshoot awful exported resources performance in puppet and is there anything I can tweak to get it to run under 10 minutes in larger environments? I have a fairly modest environment (118 nodes, but prod will be at least twice as large). I''m trying to move my distributed nagios setup to one based on

I''m very interested in the way that puppet appears to be able to generate nagios configurations though I can''t seem to find any documenation on how it works: http://reductivelabs.com/trac/naginator is clearly a placeholder page... Meanwhile the various pieces of info at links such as: http://reductivelabs.com/trac/puppet/wiki/TypeReference#nagios-host are just teasing me.

...s this and does a puppet node clean $hostname which in turn is picked up by nagios on its next run and purged. This is the section of the nagios config that I am using to both populate and purge the items from the nagios files. # collect resources and populate /etc/nagios/nagios_*.cfg Nagios_host <<||>> { notify => Service["nagios3"] } Nagios_service <<||>> { notify => Service["nagios3"] } resources { "nagios_service": notify => Service["nagios3"] purge => true, } resources { "nagi...

I''ve tried to achieve my overall goals with several different features of Puppet, but I''ve hit a bit of a wall here. I think it''s time for me to explain what I''m trying to accomplish: I want the enabling of a service in my manifests to configure the monitoring of that service by a nagios server, without needless repetition. Let me explain how my

We were using Naginator resources like nagios_host, etc. along with stored configurations and exported resources. Worked pretty well. However we have to separate the Puppet master and the Icinga (Nagios) server. They will be on different machines from now on. Are there any best practices for such a scenario? I already thought about some kind of ...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I''me using nagios builtin types and I''m very surprised that the parameter *name* is not available for type nagios_host ?!? This parameter is required to use inheritance (http://nagios.sourceforge.net/docs/3_0/objectinheritance.html) and I don''t understand why it is not included in all nagios types ? Maybe someone has an explanation or it is simply a bug? Regards, Mathieu -----BEGIN PGP SIGNATURE----- Ve...

...here run into this and fixed it? I''m curious to see what others came up with to fix this. For those that are curious as to how I fixed the "wrong file" problem I came up a solution where in my site.pp file I have the following: if ( $operatingsystem == "Debian ) { Nagios_host { target => "/etc/nagios3/conf.d/puppet_hosts.pp" } --- etc --- } -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email...

...w added loads of Nagios host and service checks like this: @@nagios_service { "check_smtp_${hostname}": check_command => "check_nrpe!check_smtp", host_name => "$fqdn", service_description => "SMTP", } and then I collect them like this: Nagios_host <<||>> Nagios_service <<||>> Nagios_hostextinfo <<||>> Nagios_servicedependency <<||>> But today I spotted that my Nagios configs in /etc/nagios/ haven''t actually been updated for ages. I''ve prodded at the puppet server and client...

...nagios, ; } service { nagios3: ensure => running, alias => nagios, hasstatus => true, hasrestart => true, require => Package[nagios], } # collect resources and populate /etc/nagios/nagios_*.cfg Nagios_host <<||>> Nagios_service <<||>> Nagios_hostextinfo <<||>> class target { @@nagios_host { $fqdn: ensure => present, alias => $hostname, address => $ipaddress, use => "generic-host", }...