On Tuesday 20 December 2016 at 21:38:44, Volker Janzen wrote:
> I see. I just do not understand yet how new commands are added to a
> satellite. There must be some binary or script on the satellite that needs
> to be executed. Will this be configured on the master and/or satellite
> with top-down?
Here's a hint for *any* Icinga2 system as soon as you start using the Master -
Satellite - Client hierarchy:
- rename /etc/icinga2/conf.d to something like /etc/icinga2/conf.d.dist (it
doesn't really matter what, just change its name)
- create a new, empty /etc/icinga2/conf.d and leave it empty
- do this on *every* machine in your network (Master, Satellite/s, Client/s -
all of them)
Then create one directory per Zone name under /etc/icinga2/zones.d and put all
the configuration files (such as the Host definitions) which are specific to
that
Zone in there - you can name the files anything you like so long as they end in
.conf
Second hint - make sure all machines in your network have an entry in
/etc/icinga2/zones.conf:
object Zone "global-templates" { global = true }
- then put any Service and ServiceCheck definitions (not Hosts) which apply to
more than one Zone into files under /etc/icinga2/zones.d/global-templates
(again, you can name these anything you like so long as they end in .conf)
*That* is the way Icinga distributes top-down configurations to the Satellites
and Clients.
Hope that helps,
Antony.
--
Users don't know what they want until they see what they get.
Please reply to the list;
please *don't* CC me.
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
