On Fri, Aug 24, 2012 at 1:53 PM, Kent Shultz <[email protected]> wrote: > I'd rather have the monitoring solution collect incoming facts that are > already coming to a central location rather than reaching out to the nodes. > I suppose a cronjob on the nodes could run facter, but still it seems > redundant since Facter gets executed along with each Puppet run. Also, I > plan on deploying the monitoring server on my Puppetmaster, so it's nicer to > compare new fact values to old fact values on the same server, instead of > having nodes constantly query PuppetDB to compare new fact values against > old ones. > > But yeah, if my proposed solutions involve patching the Puppet or PuppetDB > codebase, I could see how your suggestion might be simpler. It just seems > like better practice to leverage the facts that *are already coming in*. > > Can you give me an idea of what you're talking about with running facter > node-side and comparing against values in PuppetDB?
I had a hair-brained idea for a while to expose fact values via SNMP, but I never went anywhere with it. (I realize this is tangental, but it reminded me of it) Mike > > Thanks, > Kent > > On Friday, August 24, 2012 10:29:28 AM UTC-7, Andy Parker wrote: >> >> Wouldn't having your monitoring tool watch the output of `facter >> <factname>` on the nodes that are being monitored achieve what you are >> looking for? That seems like it would be a pretty straightforward and >> uncomplicated way of doing this. >> >> On Thu, Aug 23, 2012 at 7:09 PM, Kent Shultz <[email protected]> wrote: >> > EDIT: >> > >> > ”Id like to know the best way to collect new/incoming Fact values for a >> > node and compare it to old/previous values (i.e. from a node making a >> > puppet >> > run)” >> > >> > I meant the last parenthetical bit to come after ”new/incoming fact >> > values” >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Puppet Developers" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/puppet-dev/-/JOZlrJsa0RIJ. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-dev?hl=en. >> > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-dev/-/9xfAi0KIQCMJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
