Hi steve,

So, you have all the "services" defined statically on the Nagios server?
That setup only works, I think, if you install your Nagios server at the
very end of your deployment process and all the clients are up and ready
before the server. If you do a parallel deployment, then there is a very
good chance that Nagios will refuse to start at the first run. Cheers!!

On Friday, June 28, 2013 3:57:09 PM UTC+1, Steve J wrote:

In my experience, exporting nagios_command resources doesn't work so well.
What I've found works best, is to define nagios_command{}'s directly on the
server, rather than exporting and collecting them there later.

In my setup, the only resource that export is the nagios_host. I define
commands and services on the server, and assign the services to hostgroups.
Hosts then get service checks assigned to them based on which hostgroups I
put them in (usually done via the hosts role definition). I find that this
works well, since it doesn't leave me with multiple exported nagios_service
resources for every single host, that will eventually need to get cleaned
out of PuppetDB when the host is no longer in service.

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 6 of 8 | next ›
Discussion Overview
grouppuppet-users @
postedJun 27, '13 at 4:16p
activeOct 18, '13 at 7:51a



site design / logo © 2023 Grokbase