The issue is that here we set `address` to the relation's target-address: https://git.launchpad.net/nagios-charm/tree/hooks/monitors-relation-changed#n131
Instead we should set it to the relation's ingress-address, see https://jaas.ai/docs/charm-network-primitives ** Project changed: nrpe-charm => nagios-charm ** Changed in: nagios-charm Importance: Undecided => Medium ** Changed in: nagios-charm Status: New => Triaged -- 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/1823772 Title: nrpe uses private ip rather than public ip with nagios Status in Nagios Charm: Triaged Bug description: In K8s deployment on openstack we expose nrpe on openstack VM instances to Nagios on different bare metal model. Issue is Few of the instances uses public IPS and couple of then uses private IPs while registering with Nagios. And nagios marked those instance down in nagios which is not true. As nagios can not reach to nrpe VM instances on private network so nagios status shows critical as instance service can not reach from nagios to openstack VM instances. nrpe config as below. nrpe-host: charm: cs:nrpe options: nagios_hostname_type: host nagios_address_type: public xfs_errors: "30" swap: '' To manage notifications about this bug go to: https://bugs.launchpad.net/nagios-charm/+bug/1823772/+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
