> On 09 Sep 2016, at 09:38, Gerald Vogt <v...@spamcop.net> wrote: > > Hi! > > What's the purpose of the zone parameter in the Notification object of > icinga2? > > I thought it would say which zone sends the notifications but that seems not > the case. If you have a master-satellite setup, notifications for checks of > the satellite zone are duplicated and sent from the satellite and the master. > I find that unexpected as for checks the zone parameter defines which zone > runs the check so I have expected the same for notifications. > > So it seems to me that the "zone" parameter in the Notification object > doesn't really have a purpose. Is that right? > > We use the satellite to monitor the master and want to send out notifications > from the satellite only for the checks on the satellite…
You can safely ignore it if you are for instance using the top down config sync method in zones.d (which takes care of virtually mapping the zones directory to that zone attribute). Specifying that manually requires advanced knowledge and probably only makes sense with checkable objects (hosts, services, as mentioned in the distributed monitoring docs). The documentation table lists it just because we are documenting any attribute made available to the user, either via config object type in static config files, or inside the REST API. Kind regards, Michael -- Michael Friedrich, DI (FH) Senior Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | michael.friedr...@netways.de ** OSBConf 2016 - September - osbconf.org ** ** OSMC 2016 - November - netways.de/osmc ** _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users