Master, zone and client question

Icinga 2
1

I have a monitoring host set up, hpc-monitoring, and clients like ddn07.hpc.edu set up in a zone:

[root@hpc-monitoring icinga2]# cat zones.conf
/*
 * Generated by Icinga 2 node setup commands
 * on 2020-01-27 15:08:39 -0800
 */

object Endpoint "hpc-monitoring.hpc.edu" {
}

object Zone "master" {
        endpoints = [ "hpc-monitoring.hpc.edu" ]
}

object Zone "global-templates" {
        global = true
}

object Zone "director-global" {
        global = true
}


[root@hpc-monitoring master]# pwd
/etc/icinga2/zones.d/master

[root@hpc-monitoring master]# cat ddn07.hpc.edu.conf
object Endpoint "ddn07.hpc.edu" {
}

object Zone "ddn07.hpc.edu" {
        endpoints = [ "ddn07.hpc.edu" ]
        parent = "master"
}

object Host "ddn07.hpc.edu" {
        check_command = "hostalive"
        address = "10.125.0.79"
        vars.client_endpoint = name
}

If I go on my client and look at the debug.log I see messages like this. Why is it saying “Current zone master: ddn07.hpc.edu”? Why doesn’t it think hpc-monitoring is the zone master? The client and checks seem to work fine but there’s lots of activity in the log.


[2020-04-09 10:29:49 -0700] debug/ApiListener: Not connecting to Endpoint 'hpc-monitoring.hpc.edu' because we're already connected to it.
[2020-04-09 10:29:49 -0700] notice/ApiListener: Current zone master: ddn07.hpc.edu
[2020-04-09 10:29:49 -0700] notice/ApiListener: Connected endpoints: hpc-monitoring.hpc.edu (1)