I use NagiosXI and Puppet and have had some success in developing some interoperability without sacrificing the controls of the gui. My environment consists of linux hosts running puppet and a myriad of windows and netowrking devices which were all configured in NagiosXI via the gui.
Generally speaking, building service and host configurations for NagiosXI are the same as they were for Nagios Core. You'll use exported resources to generate configurations. To then import them to NagiosQL (what Nagios XI uses for a database in lieu of traditional nagios flat-file configurations) you place the configurations built by puppet into the import directory, which for their CentOS release is located at */usr/local/nagios/etc/import/*. You have two options for the import routine. You can use the import tool from within NagiosXI located within the core config manager, or you can use the bash script at */usr/local/nagiosxi/scripts/reconfigure_nagios.sh* The script must be executed with /usr/local/nagiosxi/scripts/ as its current working directory. I prefer the script. Others prefer the gui. The choice is yours. There's an option here to create an Exec resource for that script that then subscribes to the import directory and automate the whole procedure. The caveat is that the import directory is cleared out whenever the script is run. In effect, this will fire off that reconfigure script every 30 minutes when the nagiosxi server initiates a puppet run and populates that directory with the configuration files. For now, what I do is create a directory in which the Puppet uses as a target, then manually copy the files over as they get updated with new services/servers. My Nagios configs rarely change so it works for the level interaction I need. I'd love to hear if anyone has a more elegant ways to do this. Cheers, Sam On Wednesday, August 7, 2013 3:34:07 PM UTC-4, Ryan Bowlby wrote: > > 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 notifications. > > Has anyone made use of the puppet + Nagios XI? Would it be possible to > manage notifications within the webUI while still using puppet for > generating the host,hostgroup,service configs? > > Pagerduty isn't an option for reasons I can't get into here. > > Thanks, > Ryan > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/30fa41ee-f06b-4042-b759-9bfdd1e01bb2%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
