This document discusses combining monitoring and configuration management tools to automatically restart services when issues are detected. It recommends using Nagios for monitoring and Puppet for configuration management. High-level diagrams show the architecture, and steps are outlined for configuring Puppet classes and Nagios to monitor services and trigger Puppet to restart them when needed, allowing issues to be addressed faster than human intervention.

1. Combining Monitoring and
CM to restart services.
Greg Retkowski
Operations Engineer, OnLive

2. What's in it for me?
● It'll free you up from firefighting
● It'll react faster than a human can
● It's a hedge against technical debt

3. Required Tools
● NAGIOS
● Puppet

4. High Level Diagram

5. Our Puppet Apache Class

6. Nagios service.cfg

7. Nagios commands.cfg

8. Puppet auth.conf
● Create an empty namespaceauth.conf
● Add this to your auth.conf:

9. Puppet puppet.conf

10. Testing the puppet agent
● puppetd –listen –verbose –no-daemonize –no-
client –fqdn `hostname`

11. Invoking puppetrun
● puppetrun -a –host FQDN

12. The handle_puppetrun.sh script

13. Bringing it all together

20. Resources
http://www.rage.net/lspe