# Force command endpoint for specific service (i.e. to agent associated with other host object)

**URL:** <https://community.icinga.com/t/force-command-endpoint-for-specific-service-i-e-to-agent-associated-with-other-host-object/7434>\
**Category:** Icinga Director\
**Tags:** icinga2\
**Created:** [May 27, 2021, 6:20am UTC](https://community.icinga.com/t/force-command-endpoint-for-specific-service-i-e-to-agent-associated-with-other-host-object/7434 "2021-05-27T06:20:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shake-spear](https://community.icinga.com/user_avatar/community.icinga.com/shake-spear/32/3827_2.png) [@shake-spear](https://community.icinga.com/u/shake-spear)\
**Post date:** [May 27, 2021, 6:20am UTC](https://community.icinga.com/t/force-command-endpoint-for-specific-service-i-e-to-agent-associated-with-other-host-object/7434/1 "2021-05-27T06:20:36Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![moreamazingnick](https://community.icinga.com/user_avatar/community.icinga.com/moreamazingnick/32/7725_2.png) [@moreamazingnick](https://community.icinga.com/u/moreamazingnick)\
**Post date:** [January 17, 2022, 10:16am UTC](https://community.icinga.com/t/force-command-endpoint-for-specific-service-i-e-to-agent-associated-with-other-host-object/7434/2 "2022-01-17T10:16:28Z")

</div>

yes there will be such a feature, and it is already in the master build:

 ![2022-01-17 11_01_43-Icinga Web](https://community.icinga.com/uploads/default/original/2X/8/85e81840f81ceaa73d62cc0f80c5a102dc7d8e59.png)

With that you can create a Virtual Host → which online status can be determinded by check\_ping from icinga master node, and all other services will run on any agent endpoint you define.

---

<div class="post-metadata">

**Author:** ![Duffkess](https://community.icinga.com/user_avatar/community.icinga.com/duffkess/32/6927_2.png) [@Duffkess](https://community.icinga.com/u/Duffkess)\
**Post date:** [January 30, 2024, 3:27pm UTC](https://community.icinga.com/t/force-command-endpoint-for-specific-service-i-e-to-agent-associated-with-other-host-object/7434/3 "2024-01-30T15:27:24Z")

</div>

Is this now actually implemented? I could not find anything related yet? I have the latest director version and it is not available (v1.11.0)

---

<div class="post-metadata">

**Author:** ![moreamazingnick](https://community.icinga.com/user_avatar/community.icinga.com/moreamazingnick/32/7725_2.png) [@moreamazingnick](https://community.icinga.com/u/moreamazingnick)\
**Post date:** [January 30, 2024, 3:42pm UTC](https://community.icinga.com/t/force-command-endpoint-for-specific-service-i-e-to-agent-associated-with-other-host-object/7434/4 "2024-01-30T15:42:19Z")

</div>

Sorry for that, this feature must be enabled in the settings, and it doesn’t work like that. it more or less a renaming feature:

 ![Screenshot 2024-01-30 164129](https://community.icinga.com/uploads/default/original/2X/c/c207a2b0b653b4331c101f88ad72111c614e8ae4.png)