On Thu, Nov 11, 2010 at 4:09 PM, Tim <tedwa...@eso.org> wrote: > Hi, > > I was wondering how people here monitor puppet runs on the clients. > For puppet 0.25.x I enabled reporting and then wrote a nagios plugin > to parse the YAML report files that each client returned after a run. > Specifically I was looking for any 'failures' or 'failed_restarts'. > > Unfortunately with 2.6.2 the format of those YAML files has not only > changed but also varies hugely for different hosts depending on how > the run went. Plus the sheer size of these files now means it takes > too long for PyYAML to parse them (even for only 40 odd hosts). > > In fact, I don't understand what the YAML reports are useful for - > they don't appear to realistically be either human or machine > readable. > > Anyway what other approaches are there? I'd like to simply see 2 > things: > 1) If there were any failures during the puppet run on the client > 2) When the last puppet run on each client was (ie. if it was more > than 50 mins ago raise a warning) > > Some users of foreman, already utilize its API [1] to provide that same information to nagios.
Ohad [1] -http://theforeman.org/projects/foreman/wiki/API -- > 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. > > -- 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.
