I'm not sure if you need a setup like this if you just have a master and some 
clients. I'd would also work if you create all your configs 
(client-hosts/services) in the master zone and then work with command_endpoint. 
An example might look like this:



template Host "default-host-client" {

        check_command                   = "cluster_client" ( This is the perl 
script )

        max_check_attempts              = 5

        check_period                    = "24x7"

        check_interval                  = 3m

        retry_interval                  = 2m

        enable_notifications            = true



object Host "client1" {

        import "default-host-client"

        address                 = "1.2.2.3"



        vars.remote_client      = " client1.fqdn.local "

}



apply Service "CPU" to Host {

        import "default-service"



        check_command                   = "cpu"

        command_endpoint                = host.vars.remote_client



        assign where host.vars.remote_client

}



object Endpoint " client1.fqdn.local " {

}



object Zone "client1.fqdn.local " {

        endpoints = [ " client1.fqdn.local.com" ]

        parent = "master"

}



Regards

Reto





-----Ursprüngliche Nachricht-----
Von: icinga-users [mailto:[email protected]] Im Auftrag von 
Per-Henrik Lundblom
Gesendet: Dienstag, 1. Dezember 2015 14:49
An: [email protected]
Betreff: Re: [icinga-users] Using cluster-zone check for host state



* Per-Henrik Lundblom <[email protected]<mailto:[email protected]>> [151201 
13:12]:

> Many thanks Reto! I actually got the host state checks working as

> desired after moving the client[12] Host object definitions to the

> master zone config dir. Had to read Marcus reply four times to really

> take it in though...



Darn, of course it didn't work as expected. By moving the cliest[12] Host 
objects to the master zone config dir, _all_ client checks are skipped and 
replaced by the checks run on master1.



Back to the original problem. Marcus suggested adding new Host objects to 
master zone config with the cluster-zone checks. As I understand it, this isn't 
possible without creating new Host objecs with other names in the master zone 
config. Right or wrong?



/PH



--

Per-Henrik Lundblom           email: [email protected]<mailto:[email protected]>

phone: +46 707 647050         webpage: www.whatever.nu<http://www.whatever.nu>

_______________________________________________

icinga-users mailing list

[email protected]<mailto:[email protected]>

https://lists.icinga.org/mailman/listinfo/icinga-users
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to