My issue isn't easily described in a few config snippets, that's why i didn't include any so far. But i'll try to describe my implementation as close as possible.
Let's assume we have 3 sites (a, b and c). Site a is running the parent zone, we call it "root" (and also a global configuration zone called "global-config"), the endpoint is called "master". Endpoint "satellite-b" is running zone "site-b" whose parent is my zone "root". Endpoint "satellite-c" is running zone "site-c" whose parent is my zone "root" as well. All config is done on my endpoint "master" (in the corresponding zone directories), which is replicated to my endpoints "satellite-b" and "satellite-c". Each satellite is only monitoring other systems at its local site. Additionally, i would like all notifications related to systems at site b to be sent from "satellite b". Same goes for site c, all notifications related to systems at site c should be sent from "satellite c", I've put all notification apply rules in each zone for each site, assuming that the notifications will be executed by the endpoint which is located in that zone. This leads me to my main issue, sometimes notifications for a host at site b or c are being sent out by my _master_ endpoint, but i would have expected that only "satellite-b" should send notifications for zone "site-b". Strangely enough, it appears very random if a single notification is being sent from master or the "correct" satellite. As of now, i have only found 2 ways of making sure that the master won't send any unexpected notifications: - disable notification feature on master (not cool) - using the following expression in my notification apply rule: assign where ZoneName == "site-b" The second way isn't really nice either, since the master doesn't know about any notifications happening in the child zones. Also i regularly see messages like these in my master log: - checking for notifications for checkable xyz - checkable xyz does not have any notifications So i'm searching for the proper way to make sure that master won't send notifications for zones "site-b" and "site-c". If my descriptions should not suffice, please let me know what more info i can provide. Regards, Markus Sent from my iPhone On 16 Apr 2015, at 22:47, Michael Friedrich <michael.friedr...@netways.de <mailto:michael.friedr...@netways.de> > wrote: Reading your mails again and again but I still don't understand the issue - it doesn't shed some light into the problem, especially not with the assumptions made without any configuration snippets (and object list output) and relevant (debug) log parts - and I won't do blind guessing. Von meinem iPad gesendet Am 16.04.2015 um 15:38 schrieb Markus Joosten <markus.joos...@plumbe.de <mailto:markus.joos...@plumbe.de> <mailto:markus.joos...@plumbe.de <mailto:markus.joos...@plumbe.de> >>: It appears i spoke to soon. This behaviour is really weird and sort of erratic. After a few reloads of Icinga2 on my master and the endpoints, i am now receiving notifications from my master again. This time, master and satellite seem to take turns in sending the notifications (1 from the master, 1 from the satellite, and so on). I'd really appreciate some feedback regarding this. Regards, Markus -----Original message----- From: Markus Joosten <markus.joos...@plumbe.de <mailto:markus.joos...@plumbe.de> <mailto:markus.joos...@plumbe.de <mailto:markus.joos...@plumbe.de> >> Sent: Thursday 16th April 2015 14:29 To: Icinga User's Corner <icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> <mailto:icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> >> Subject: Re: [icinga-users] Restrict notifications to one specific (satellite) endpoint Hi list, this is just a follow-up to my previous issue with restricting notifications to the proper endpoints since i might have found the reason for this behaviour. A quick recap: - i'm running a distributed setup with a global-config zone which holds templates, commands and such - the cluster master should only monitor all its child endpoints, the actual host and service monitoring should be performed by the endpoints in their zones - when assigning Notification objects to hosts, the cluster master would always send *some* of the notifications The workaround (by using: assign where ZoneName == ...) helped so far that the notifications were always sent by the correct endpoint, but without the master "knowing" about them. (There was no notification object visible on the master using "icinga2 object list --type Notification", all GUIs always showed 0 notifications for the hosts and services being monitored from my satellites.) Today i disabled the import of the mail-host-notification template (which was defined in my global-config zone) and voila, notifications were only sent from the correct endpoint. My theory is that somehow the master thinks he is responsible for a notification because its template is defined in the global-config zone. Could that be the case? Would that be a desired behaviour or a bug? Looking forward to a reply :) Regards, Markus -----Original message----- From: Markus Joosten <markus.joos...@plumbe.de <mailto:markus.joos...@plumbe.de> <mailto:markus.joos...@plumbe.de <mailto:markus.joos...@plumbe.de> >> Sent: Monday 2nd February 2015 10:26 To: Icinga User's Corner <icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> <mailto:icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> >> Subject: Re: [icinga-users] Restrict notifications to one specific (satellite) endpoint Markus, thanks alot for pointing me in the right direction! Whilst using host.zone did not change the behaviour, i've been able to restrict the notifications to specific endpoint(s) by applying the notifications using constants as such: apply Notification "host-notify-by-mail" to Host { [...] assign where host.vars.notification.mail && ZoneName == "satellite-zone-2" } (using NodeName instead of ZoneName works as well) Best regards, Markus -----Original message----- > From:Markus Frosch <mar...@lazyfrosch.de <mailto:mar...@lazyfrosch.de> > <mailto:mar...@lazyfrosch.de <mailto:mar...@lazyfrosch.de> >> > Sent: Saturday 31st January 2015 17:26 > To: Icinga User's Corner <icinga-users@lists.icinga.org > <mailto:icinga-users@lists.icinga.org> <mailto:icinga-users@lists.icinga.org > <mailto:icinga-users@lists.icinga.org> >> > Subject: Re: [icinga-users] Restrict notifications to one specific > (satellite) endpoint > > On 31.01.2015 14:47, Markus Joosten wrote: > > thanks alot for your response. > > Actually i would like the master _not_ to notify for hosts in the satellite > > zones. > > Only the satellite endpoints should generate alerts for the hosts in their > > zone. > > > > The master should only generate alerts for hosts located in the parent zones > > > > As i've written before, it seems to be impossible to accomplish this - the > > master always sends notifications for the child zones as well. > > > > Unless i disable the notification on the master, which is not what i want > > of course. > > That should be doable with different notification rules for master and > satellite, or a const helper. > > The attribute host.zone is internally set due to the zones loading. > > apply Notification ... { > ... > assign where host.zone == "master" > //assign where host.zone == ZoneName > } > > Have not tested this! > > But please try and give us feedback. > > Cheers from FOSDEM :) > Markus > > -- > mar...@lazyfrosch.de <mailto:mar...@lazyfrosch.de> > <mailto:mar...@lazyfrosch.de <mailto:mar...@lazyfrosch.de> > > http://www.lazyfrosch.de <http://www.lazyfrosch.de> > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> > <mailto:icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> > > https://lists.icinga.org/mailman/listinfo/icinga-users > _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> <mailto:icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> > https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> <mailto:icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> > https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> <mailto:icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> > https://lists.icinga.org/mailman/listinfo/icinga-users -- Michael Friedrich, DI (FH) Application Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de <http://www.netways.de> | michael.friedr...@netways.de <mailto:michael.friedr...@netways.de> ** OSDC 2015 - April - osdc.de <http://osdc.de> ** ** Puppet Camp Berlin 2015 - April - netways.de/puppetcamp <http://netways.de/puppetcamp> ** ** OSBConf 2015 - September - osbconf.org <http://osbconf.org> ** _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org> https://lists.icinga.org/mailman/listinfo/icinga-users
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
