I use foreman dashboard and summarized emails. I have a runinterval of 2 hours. So, if any host has not reported for more than 2 hours. Then that is a warning sign, time to fire up SSH. :)
Also, zenoss is configured to monitor some of the services. But, right now it is not monitoring puppetd. On Thu, Dec 17, 2009 at 10:04 AM, Sukh Khehra <skhe...@proofpoint.com>wrote: > Hi, > > > > I was wondering what people out there are doing to monitor puppetd in large > environments. I’d love to hear what the best practices are around this. > > > > We have a few hundred hosts and are currently looking at the timestamps on > the yaml files in /var/lib/puppet/yaml/facts/ on puppetmasters to make sure > all clients are alive. Is it true that for a given client the fact file on > the puppetmaster will always get updated on every one of its puppet runs? Or > does it update only when facts change. > > > > Thanks, > > Sukh > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- LOhit -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
