On Sun, Jun 24, 2012 at 03:45:50PM -0500, Kyle Sexton wrote: > All, > > I'm curious what monitoring solutions everyone is using and recommend, some > of the ones I've been looking at recently: > > Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive > solution (have to have add-ons for graphing, etc..) > Zabbix: Currently using, decent but seems to be a bit resource intenstive > Zenoss: Never used, no opinion yet > Icinga: Never used, Nagios fork that I have no opinion on yet > Shinkin: Never used, no opinion yet > Centreon: Never used, no opinion yet
OpenNMS[1] is my personal favourite at the moment. It has a bit of a learning curve but works great once you get over it. In terms of configuration I manage OpenNMS config itself in puppet but when it comes to configuring nodes for monitoring I use the automated service discovery capabilities of OpenNMS. Once you 'teach' it about the services you're running and how to discover them it's just a case of triggering a service scan after a node is built. I do this via a REST call after the initial puppet run. OpenNMS will periodically re-scan my nodes and pick up any changes (or one can trigger a re-scan manually when/if needed). I tried many things before but OpenNMS works best for me so far. Cheers, Andrew. [1] http://www.opennms.org/ -- [ a...@zx23.net ] -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
