On Thursday 08 December 2016 at 00:43:31, isaac rodriguez wrote:
> Thanks, this has been very insightful. Lastly, with respect to the
> "aggregate check" constructed by Michael Martinez, where would that
> function be defined? conf.d/services.conf on the master node?
> conf.d/notifications.conf?
In general, for a distributed setup, you won't have anything (or very little)
under conf.d on the master node.
Anything specific to remote zones goes under /etc/icinga2/zones.d/ZONENAME
Anything which applies to all nodes goes under /etc/icinga2/zones.d/global-
templates (which should be defined as a zone in /etc/icinga2/zones.conf on all
endpoints with the setting "global = true").
What name you give to the file containing the functions is actually irrelevant.
Icinga will treat the contents of all files ending in .conf equally.
> Is this type of check possible with a bottom-up approach? Or should I
> use a top-down?
Bottom-up means you have to define all the checks on the endpoints, and the
master then gets to know about the results.
I've never found a good reason to use this, so I'm not familiar with setting
things up this way. It just seems too tedious to me.
Antony.
--
I have an excellent memory.
I can't think of a single thing I've forgotten.
Please reply to the list;
please *don't* CC me.
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
