----- "Al @ Lab42" <lab42...@gmail.com> wrote: > Hi List, > I would like to discuss with whoever is interested one topic that I > suppose has general interest. > > I want to implement some kind of automatic testing on the status of a > node after a Puppet Run. > These tests involve trivial and less trivial things things like: > - A local service is running > - A local port is open > - A remote server on a remote port is reachable by the node > - An URL replies with an expected content > - Some specific function needed by the node and provided by a remote > host is working (ie: ldap acces for users authentication, ntp > sync...) > - Whatever other check that asserts that the node is correctly > working
sounds like things you want to monitor anyway in an ongoing manner? So assuming you have monitoring for all of this, is the problem that you want visibility of the state right now after a run and not when nagios gets round to doing its next checks which might be many minutes? I favor nrpe - cos I can deploy my check logic with puppet - but I really think you want your monitoring to cover all of this. To answer the 'now' part of it, I'd just notify via mcollective my nagios box to do a check for all services on the node post puppet run. -- 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.
