We have a setting with hosts hosting services for different customers:
Physical Host “phyhost”
service A: customer 1
service B: customer 2
To handle downtimes on a per customer basis we created following setup in director:
-
Physical Host “phyhost” (agent based monitoring)
- a lot of service checks relevant for the host itself -
“Hosted Host” “cust1host”
object name is phyhost_cust1host, the address is the address of “phyhost” -
“Hosted Host” “cust2host”
object name is phyhost_cust1host, the address is the address of “phyhost”
Now there are some checks (e.g. disk_checks) that needed to be executed on “phyhost” but should be associated with the “Hosted Host” hosts.
e.g.
- “Hosted Host” “cust1host”
check_ping → running on master
check_disk → running on “phyhost”
I tried to figure it out by reading docs and other threads in this forum, but …
I just ended up with a vague picture about command_endpoint - but I found no way to configure it in Icinga Director on a service or service template (we are using a agent based setup already - works fine!)
Is something like a servicetemplate with customvar “phyhost” + command_endpoint = $phyhost$ possible to pin specific checks to a specific endpoint?
