Wondering if anyone has written a nagios or icinga puppet module that
uses native Foreman data rather than storeconfigs to populate the
nagios configs?
(Guessing not, since Google is coming back with basically nothing).
Thanks,
Brian
Hello,
Not quite what you are looking for but there is that :
https://github.com/favoretti/puppetdb-external-naginator
It uses puppetdb as storeconfigs but don't use buggy naginator to collect
data and write nagios configuration.
Regards,
Romain
···
2013/10/29 Brian GuptaWondering if anyone has written a nagios or icinga puppet module that
uses native Foreman data rather than storeconfigs to populate the
nagios configs?(Guessing not, since Google is coming back with basically nothing).
Thanks,
Brian–
You received this message because you are subscribed to the Google Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
I need this too but finding nothing. I really don't want to go back to
PuppetDB…
···
On Tuesday, October 29, 2013 4:07:56 AM UTC-4, Brian Gupta wrote: > > Wondering if anyone has written a nagios or icinga puppet module that > uses native Foreman data rather than storeconfigs to populate the > nagios configs? > > (Guessing not, since Google is coming back with basically nothing). > > Thanks, > Brian >I guess I wasn't clear. Basically I am looking for a module that can
build nagios/icinga configs, without using Puppet "exported
resources". (I am trying to see if I can do this without storeconfigs
or puppetdb).
(I already have it working using "exported resources" but want to see
if it's possible to do this with just Foreman native data. I am
already exporting all facts directly into Foreman.)
Thanks,
Brian
···
On Tue, Oct 29, 2013 at 4:54 AM, Romain Vrignaud wrote: > Hello, > > Not quite what you are looking for but there is that : > https://github.com/favoretti/puppetdb-external-naginator > It uses puppetdb as storeconfigs but don't use buggy naginator to collect > data and write nagios configuration. > > Regards, > Romain > > > 2013/10/29 Brian Gupta >> >> Wondering if anyone has written a nagios or icinga puppet module that >> uses native Foreman data rather than storeconfigs to populate the >> nagios configs? >> >> (Guessing not, since Google is coming back with basically nothing). >> >> Thanks, >> Brian >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-users+unsubscribe@googlegroups.com. >> To post to this group, send email to foreman-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/groups/opt_out.Unfortunately nothing has come up since, so we just basically brought
a leaf PuppetDB node into our environment just to support this one use
case. 
It's frustrating but I think that's the only option that
doesn't involve a huge amount of work.
-Brian
···
On Tue, Jul 29, 2014 at 2:00 PM, Edson Manners wrote: > I need this too but finding nothing. I really don't want to go back to > PuppetDB.... > > > On Tuesday, October 29, 2013 4:07:56 AM UTC-4, Brian Gupta wrote: >> >> Wondering if anyone has written a nagios or icinga puppet module that >> uses native Foreman data rather than storeconfigs to populate the >> nagios configs? >> >> (Guessing not, since Google is coming back with basically nothing). >> >> Thanks, >> Brian > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.Hey Brian,
Yes, it's totally doable but it's not nearly as easy to say the least.
We have monitoring with a Nagios puppet module built using the Foreman API
to discover hosts, classes, parameters, etc. It's very specific to our
use-cases though, and not something generic that the world could benefit
from. But we essentially loop through every host discovered from the
Foreman API and have a bunch of if statements to determine which classes
are assigned to each host, and if there are any parameters associated with
those classes that determine how we should monitor the service.
We actually use the Puppet Future Parser and our manifest works like so
(bits and pieces):
class nagios {
each($foreman_api::servers) |$key, $value| {
$host_name = $value['host']['name']
$myclasses = $foreman_api::hostLevelClasses[$host_name]
# PostgreSQL
if ($myclasses['postgres']) {
$checkPostgres = true
.. some params related to PostgreSQL
}
.. etc
}
}
And then we have a template file that generates the nagios checks per host.
Pro's are that you don't need to rely on exported resources, naginator, or
any of that stuff. Con's are it takes awhile to generate the catalog for
the Nagios host (about 5 mins for 500 servers or so, on a moderated sized
VM) and it's very specific to your monitoring.
Jason