We use a dashboard -- in our case Foreman -- and watch for hosts returning anything other than complete success. Any diagnostic messages at all drop the host into "hosts that made modifications" category, and errors drop the host into "hosts in error state." I have my team watching the dashboard throughout the day and if we see hosts drop into either category, they independently look and determine if there needs to be an investigation.
The only tough thing about this is that it requires your classes to be well-behaved -- no extraneous output or debugging statements, or execs that run blindly every time. But you don't have any of those anyway in your production environment, right? ;-) -Eric On Apr 20, 4:46 pm, Pavel Piatruk <piatru...@gmail.com> wrote: > Hello! > > Even if puppet rule sets are OK, sometimes errors occur on puppet clients upon > processing puppet rules. > What are the best practices to catch/analyze them? > > signature.asc > < 1KViewDownload -- 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.
