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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I use foreman dashboard* :) it provides me an overview of all hosts in their latest status - e.g. all OK, Active(puppet did something), Error (puppet reported an error, or out of sync (puppet is not running). and of course you can get the host list when you click on each of the statuses. additionally, Foreman sends me a summarized email, e.g. all hosts and their total changes errors etc (with links to each report if you are interested in the details). cheers, Ohad [1] http://theforeman.org/wiki/foreman/Screenshots#Dashboard On Thu, Dec 17, 2009 at 12:34 PM, Sukh Khehra <skhehra@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-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Sukh Khehra 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. >Other options are Splunk or something similar for syslog checking, Nagios w/nrpe, etc. -scott -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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 <skhehra@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-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Sukh Khehra 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-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.There is a nagios plugin in the ext/ directory in the source tree. I use this, as well as the ''err'' tag to send errors in applying manifests to my group''s mailing list. -- Joe McDonagh Silent Penguin Services Operations Engineer AIM: YoosingYoonickz IRC: joe-mac on freenode Blog: www.colonfail.com -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
via nagios: /usr/lib/nagios/plugins/check_file_age -f /var/lib/puppet/state/ state.yaml -w 5400 -c 7200 On Dec 17, 4:34 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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Apparently Analagous Threads
- yet another class dependency question.
- Foreman / External Nodes -- Node Not found
- multiple puppetmasters (w/ Passenger) behind load balancer
- Puppet+Foreman: class into module couldn't apply on nodes
- Puppet agents stop reporting after master runs out of disk space...