Most of my puppet runs take ~15 seconds or so, however my Nagios servers take up to 4 minutes to complete.
On Mon, Oct 10, 2011 at 7:00 AM, Chris Phillips <ch...@untrepid.com> wrote: > > > On 10 October 2011 13:05, Jonathan Gazeley <jonathan.gaze...@bristol.ac.uk > > wrote: > >> On 08/10/11 21:22, Chris Phillips wrote: >> >>> What better way to monitor the puppet runs than by executing that run as >>> part of the check? >>> >> >> I assume your Nagios execution timeout must be insanely long? :) >> >> In the past I have considered using Nagios for things other than >> monitoring, and likewise using Puppet for things other than configuration. >> On both counts I decided it was probably best to set a boundary and not >> wilfully abuse these tools, since it's likely to go wrong sooner or later! >> In my organisation we use Nagios only to monitor, and Puppet only to >> configure. >> >> > always done within 30 seconds, and it's not like if it took longer on an > occasional rollout it would impact puppet at all, temporarily messy as the > monitor results might be. > > fundamentally though, with cron or puppetd being trivial simple, i'm more > than happy to be doing it this way. > > > Chris > > -- > 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. > -- 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.
