I’ve got a reasonably large icinga2 deployment using director and a lot of api automation, several satellite zones carrying out checks in a DMZ type area working well.
I’ve now added a 3rd satellite zone, the idea is this is on a remote machine that will monitor inbound to our network, so the plan is to add a new service to multiple existing hosts, the new service will be a simple ping4 to ping in from the satellite node.
However, the issue is that the host itself is registered to the master zone, not the satellite (I don’t want to create a second host on the satellite as the icingaweb2 gui then looks messy having 2 hosts for each one).
The error therefore on the satellite is:
[2021-07-23 15:01:26 +0000] information/ApiListener: My API identity: mysatellitehost.domain.net [2021-07-23 15:01:27 +0000] critical/config: Error: Validation failed for object 'monitor-hostname.check.net!service-EXTERNAL-ping' of type 'Service'; Attribute 'host_name': Object 'monitor-hostname.check.net' of type 'Host' does not exist.
So ideally what I want is:
– host - registered on master zone, majority of checks, services are on master
– service1 - on master
– service2 - on master
– service3 - on satellite
- Version on master r2.11.3-1, version on satellite r2.12.2-1
- Debian 9 on master, Debian 8 on satellite
- Enabled features (
icinga2 feature list)
Disabled features: debuglog elasticsearch gelf graphite influxdb opentsdb syslog
Enabled features: api checker command compatlog ido-mysql livestatus mainlog notification perfdata statusdata
Any ideas on how to easily achieve what I’m trying to do here? I need to maintain config in Director, so adding manual to conf files is not really an option due to the automation we’ve integrated with director.
Thanks in advance any suggestions!