I’m already experimenting for a while with Icinga and I can not really decide between the two configuration options.
“repository.d” - let the master of the Icinga client pull the configuration, the client makes the checks for what is set on itself, the master regularly receives an update regardless of his check periods, after a while no update comes, the master asks for an update and then goes through its normal alarm cycle.
“zones.d” - let the master of the Icinga client push the configuration, the master asks the client after his check periods, exactly the same as a host configuration in conf.d only that the client carries out the check.
Which ones do you use and why?
Chris of arcanasoft