----- Original Message ----- > From: "David Lutterkort" <lut...@puppet.com> > To: "puppet-dev" <puppet-dev@googlegroups.com> > Sent: Friday, 6 May, 2016 21:30:18 > Subject: Re: [Puppet-dev] metaparam question
> On Sun, May 1, 2016 at 11:33 AM, R.I.Pienaar <r...@devco.net> wrote: > >> Late to follow up on this but I had some time to work on this again, >> > > No matter how late you are, there's always somebody later ;) > > For the whole cross-node dependency business, we built a sqlhealthcheck > <https://github.com/puppetlabs/puppetlabs-sqlhealthcheck> provider; it's a > provider for a Sql service/capability type, but has the advantage that it > is not tied to the local db service, i.e. geared towards being used by both > on the DB node itself and nodes that need to talk to the DB. > > We did discuss extending this to make it easy to incorporate nagios checks, > but that has suffered from ENOTIME so far. so my plan with this is 2 fold, it lets people make puppet's generate state check a bit better for any resource quite cheaply but also once this is in the catalog I can write a sensu/nagios/graphite/tool of choice thing that loads the catalog and checks everything regularly and send off results to whatever they like. I think I'll have to figure out how to autorequire the plugin being called in case Puppet manages it but I think this concept is pretty powerful - and indeed should work with your cross node stuff too. Those checks you have in AO are good but the barrier to entry is quite high on making those I felt -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/678114459.450537.1462564928420.JavaMail.zimbra%40devco.net. For more options, visit https://groups.google.com/d/optout.
