I've added a preliminary 'parents' option: NRPE MP: https://code.launchpad.net/~xavpaice/nrpe-charm/+git/nrpe-charm/+merge/332126
Nagios MP: https://code.launchpad.net/~xavpaice/nagios-charm/+git/nagios-charm/+merge/332127 What this does is, for a host that is a container on a machine, and therefore has a machine name like 3/lxd/5, that will now be set with a parent of the nagios known hostname for machine 3. The limitation of this is that checks are still executed and when the parent comes back to life, we receive alerts for the child hosts being down because they're still booting up. -- You received this bug notification because you are a member of Nagios Charm developers, which is subscribed to Nagios Charm. https://bugs.launchpad.net/bugs/1722325 Title: Wishlist: host dependency and/or parents in host definitions Status in Nagios Charm: Confirmed Status in NRPE Charm: Confirmed Bug description: When we have a unit defined which is a container on a host, we want to be able to not alert for all the containers when the host those containers lives on goes down. - only when the host itself is actually monitored by the same nagios server - there is the 'parents' field in a host definition which would do this, but we don't have that info when defining the host in a container - hostdependency definitions could work? To manage notifications about this bug go to: https://bugs.launchpad.net/nagios-charm/+bug/1722325/+subscriptions -- Mailing list: https://launchpad.net/~nagios-charmers Post to : [email protected] Unsubscribe : https://launchpad.net/~nagios-charmers More help : https://help.launchpad.net/ListHelp
