similar to: Managing multiple nagios servers with puppet and virtual resources

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

Nagios support "custom object variables" (http://nagios.sourceforge.net/docs/nagioscore/3/en/customobjectvars.html) buy prefixing them with an underscore: define host{ host_name linuxserver _mac_address 00:06:5B:A6:AD:AA _rack_number R32 } However, I can''t determine how to use these with puppet nagios resources. I''m assuming they aren''t supported, but

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 ''rsync'' of the configuration from

Folks: I''ve started to play around with the comprehensive integrated module set from example42 (http://www.example42.com/). Following the instructions, I set up one node as a nagios server, with ''include nagios''. I set up another node to be monitored via nagios, with ''include nagios::target". I set $monitor=true for the base node, which is inherited by

I have to rebuild a new Nagios box and thought this might be a good time to migrate away. I use snmp mostly for everything but with the fork Nagios endured I wonder about putting any more effort into the project. I probably should look at OpenNMS again, but the other options I think might work are Icinga (Should be trivial to migrate) or Zenoss or maybe even Zabbix? Anyone have experience in

Hello all, I am trying to write a script that will check logs for puppet errors to use in a nagios check. I am checking /var/log/messages (RHEL6) but when puppet runs on its 30 minute interval, nothing gets written to messages. I have also looked at /var/log/puppet/puppet.log but that does not seem to be consistent either: [root@gm10v nagios]# tail /var/log/puppet/puppet.log Wed May 02 14:27:47

On my network management server I have Name : nagios-plugins-nrpe Arch : x86_64 Version : 2.13 Release : 1.el6 Size : 38 k Repo : installed From repo : epel To my dismay I noticed that this doesn't seem to support IPv6: [ts at bombur ~]$ host galadriel.example.com galadriel.example.com has IPv6 address 2001:db8:f004:8::32 [ts at bombur ~]$

So, my favorite RPM repository (EPEL) only has the ancient nagios-2.12 or so. What's the repo you use for Nagios 3? -- Florin Andrei http://florin.myip.org/

Hi all Here is the 0.24.7 release - the last of the 0.24.x branch and codenamed Gonzo. You can download it here: http://reductivelabs.com/downloads/puppet/puppet-0.24.7.tgz Big tickets items in the release are: * Manifest documentation http://reductivelabs.com/trac/puppet/wiki/PuppetManifestDocumentation This new functionality creates documentation from marked up manifests and modules and

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

I''m sure people have hit this problem before. In my nagios module, the nagios command pipe file at /var/lib/nagios3/rw/nagios.cmd is owned by the nagios user, but needs to be written to by the www-data user. Adding the www-user to the nagios group is one solution, but that requires that the nagios module potentially modify the www-data user, which seems bad. What''s the best way

Hi, I''m new to Puppet so may be going about this completely the wrong way, or perhaps it is an selinux problem rather than a Puppet problem. I have a problem copying a file and changing the seltype. I don''t think it is Nagios specific. Code is something like: file { ''/usr/sbin/nrpe'': source =>

Hi List, I have noted a number of times, various comments on this list about Nagios, hence my questions. just been employed by an ISP and they want to upgrade their fairly extensive nagios monitoring. They are mostly an ubuntu lts shop, so 1st question What advantages does the RH/CentOS world have (if any?) over the ubuntu LTS world? They are talking about running the server on a vm, as I

Hello ! I''m trying to implement a Nagios solution based on David Schmitt''s Complete Config. But I the following error when running puppetd -t - v : notice: Starting catalog run err: //Node[monitoring]/nagios::target/Nagios::Host[]/File[/conf.d/ _host.cfg]/ensure: change from absent to present failed: Could not set present on ensure: No such file or directory - /conf.d/

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 =>

So I''m revisiting puppet''s management of nagios now that 0.25.1 is out and I want to say thanks for the updates to all the nagios types. However, there is one huge, gaping hole that''s been asked about before in 2 different threads but that''s never been addressed: object inheritance. For it to work, it requires the object being inherited from to have a

-----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

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

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 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