everything using Puppet • Forget add the monitoring • Because someone else did it, didn’t they? • Machine fills up the disk • Kills the database • No alert was ever sent out Monday, 8 April 13
the equation • Don’t let them touch the monitoring system • Unless they really really really have to • Use Puppet / Puppetdb • Don't use the naginator type • Sorry luke Monday, 8 April 13
automatically (not out of sync) • Do this configuration in the same place (obvious) • Should hide the implementation • Use configuration data fro monitoring config Monday, 8 April 13
@@file { "/etc/nagios/conf.d/$::fqdn.apachecheck.conf": content => "nagios check stuff \n", tag => "nagioscheck", } #Install all our webserver stuff as well } Monday, 8 April 13
the hosts with a class of Apache with a model of 17* and are in the dc uk • Uses facts • file (‘ukmonitoringapache’: • ensure=>present, content=>(‘template/apachecheck.erb’) path => ‘/etc/nagios.d/check/apache.conf‘) Monday, 8 April 13