similar to: Setting nagios hostgroups based on included classes

Hi everyone, I am reconsidering how I am using the Puppet nagios functionality, at the moment I am creating one service for each check on each host. A lot of them are identical, and would be better tied to hostgroups to simplify my config. Namely, I have about 5,000 checks in there now which will go up to about 20K over the next month, and it''s taking about 5-10 minutes for a Puppet

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

I am using stored configs to manage my nagios host and services checks and I have run into a problem that I have been unable to solve. When the stored configs are purged from puppet the nagios server correctly removes them from the services and hosts file but does not notify the nagios service and instead throws an error. So the entries are still there and nagios still reports on them until

Hi all, I''m working on setting up Puppet to write out my Nagios configs. A few weeks back I inserted a few dummy Nagios checks into my Puppet config, and the Nagios configs were written out properly. I''ve now added loads of Nagios host and service checks like this: @@nagios_service { "check_smtp_${hostname}": check_command =>

I am trying to create a hostgroup using the Foreman API (foreman-0.4-0.1rc1.noarch): Using perl v.5.14.2, REST::Client et. al., ending up with sending: POST /hostgroups {"name":"api-created-

Hello ! I''m using a lot of nagios_ commands in my puppet manifests and I saw a problem when using ''undef'' in exported resources : Here is a simple example : define nagios::service::distributed ($ensure=present, $service_description, $host_name=false, $contact_groups=false) { nagios_service {$name: ensure => $ensure, use =>

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. There''s a servicegroups parameter

Hi all, For months now I''ve been using Puppet with PuppetDB backend to manage my Nagios configs. We now have 1200+ services being checked and including servicedependency, host, hostdependency, command and other Nagios resources being managed, that''s about 3000 resources in total. Unfortunately this means the monitoring server takes about 8 minutes to perform a Puppet run.

Hi folks, For the first time since I started playing with puppet 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 <<! !>>

It seems that the nagios_service type will not write out the "name" property of nagios service objects. I had thought this was an oversight or a bug, till I saw this thread: http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg10387.html which seems to imply that this is a deliberate "feature". Is this prohibition on "name" really the desired behaviour?

Hi All, I currently make use of Icinga (nagios fork) + Puppet for fully automated monitoring. It''s worked great up to this point. I''ve recently been asked to integrate fine grained notifications support into icinga. I''m not entirely sure puppet manifests are the right place to manage contacts, contact groups, and their use within host and service definitions for

Hi, I''m happily aware of the way that there is no concept of unmanaging something and when this is in the context of a file ownership or whatever, then that makes sense. But when this is applied to things like nagios configuration data the principle seems to come unstuck. Or at least, it seems so to me. Say I have a nagios_service which uses another template nagios_service. I am about

This module does basically what I have done in the very beginning. Create an empty directory as a preparation step for the configuration files. But this configuration also did not regenerate the files. Seems, I will stick with my workaround and delete the files manually and the restart the Puppet agent. If anyone is interested in details, see: http://wp.me/p1RukY-1n. Thanks for helping, Gabriel!

Running puppet 2.6.11 opensource on Red Hat 5.6 client. I cannot explain this logically but I have a directory structure like so: /etc/puppet/manifests/hiera/hostgroups/ with directories for each of my application areas like so: *clickz core devel dns icross iswap itch puppet test ubuntu* *What is weird is that if I put anything under the directory named "core", the ext

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

I am trying to supplement and ultimately provide a patch for ''foreman'' which is an adjunct to puppet. Essentially, there is a Hosts class which belongs_to Hostgroup and Hostgroup class has a column called ''ancestry'' which is actually a Hostgroup (probably what is referred to as STI but I am not sure) and thus within Foreman, nesting Hostgroups is not uncommon.

Hi, I''m having a problem with extlookup not respecting the ''certname'' parameter[1].  When executing a puppet run with either the --certname or --fqdn parameters, it ends up using the specified SSL certificate and gets the correct node definition applied from the puppetmaster.  However, it still retrieves extlookup data using the node''s actual FQDN, not the one

2008/5/14 Thomas Harold <tgh at tgharold.com>: > Sergio Belkin wrote: >> >> 2008/5/13 <jleaver+centos at reachone.com>: >> >> OK, you won :) I'm going to test nagios. I am using centos 5.1 >> x86_64. Do I lose much if I use rpm from rpmforge (version 2.9)? >> > > We're running version 2.11 at the office (on CentOS 5.1 x86_64).

Hi I just installed nagios et al[1] in my Centos-5.2 (x86). When I try to test the configuration file it fails[2] with the message "Unexpected token or statement(...)". The line is: command[notify-by-email]=/usr/bin/printf "$OUTPUT$" | /bin/mail -s '$SERVICESTATE$ alert for $HOSTALIAS$/$SERVICEDESC$' $CONTACTEMAIL$ But if I comment this line, then I got the same

Hi Steve Thanks for all your help, i followed your answers and found on that nagios was being run as user nagios....and if i executed the last command it asked for a password [i tried nagios password,root password etc] but it did not work..it the end i opened nagios.cfg and changed the NAGIOS_USER to root and changed the ownership permissons on the script also to root..I now get the correct