icingaweb2-module-director
icingaweb2-module-director copied to clipboard
Icinga
Allow user to specify command_endpoint
At present, the director only allows a Yes/No option to determine whether the check runs on the icinga agent and it sets the command_endpoint = host_name. I would like to be able to choose the specific command_endpoint presumably from a drop down list of icinga agents.
Absolutely makes sense to me, just: a dropdown with all hosts will hurt people with lot's of them. Once we implemented feature #606 this can be added easily.
Feature would be very helpful. Right now we need to add services with specific endpoints by configuration files. Since this services are not visible in director, it's sometimes difficult to get an overview of configured services for hosts in director. +1 Vote:)
Also +1 :) That would be very helpful - I need to set command_endpoint for specific services to force the commands to only run from a specific agent. I have different agents in place e.g. one for windows checks only and one for SNMP checks where the host IP needs to be allowed in SNMP settings on the host to be checked
Hi. I have the need to add a different command_endpoint within a service definition. I would appreciate if you could add this feature in one of the next releases. :)
Hi, Is there anything new with possibility to "Allow user to specify command_endpoint" ? I have Director v1.4.3 and haven't tried github master lately. It could be handy, because I have several zones, and when tunnel between master zone and satellite zone is dropped I have no info about web checks, because they are scheduled on satellite..
+1 Vote. Looking forward to select the command_endpoint explicitely on director to run remote checks out of defined network zones.
+1 We really like to see this feature in the Icinga 2 Director as well. In some circumstances we need to set the command endpoint in a service template to one dedicated cluster member, like it's already possible for host templates.
+1 Vote I just wanted to open another bug for this problem as i saw this issue. Here we have the need to schedule some services for the parent zone/endpoint. As this is perfectly easy to be configured in icinga2 i think it would be also good to have it implemented in director as well. Thx
@Thomas-Gelf Created pull request #1817 for this. Please let me know what you think.
Hello @pbngl
First of all thank you for working on this feature! This is awesome!
I have quick question: is it possible to use custom variable from object Host to update command_endpoint dynamically? Is it a complicated changes?
+1 Vote. Waiting for the Director solution. Use this several times in .conf files.
I got the info that in large environments it is a problem to create the drop-down or autocompletion list. This would be the show stopper to integrate this requirement. But drop-down or autocompletion list is not necessary. If I select "host.name = " from the services in "assign where", I only have one free field to enter the hostname.
+1. This is making me crazy right now. It is impossible to have a mixture of services checked through the agent and remotely from the master (e.g. check a TCP port is reachable) with Director right now, that's a pity =(
What is the workaround for this, to be able to use Icinga Director for everything but also change the command_endpoint for a service template or service set? I have some checks on a host that need to be run from a different zone.
my workaround: I define the service in Director, disable the Service in Director, copy the Preview lines in an *.conf file on the master and add the the command_endpoint line.
And I write an comment in the disabled service, that other know why they can see the service in dashboard.
my workaround: I define the service in Director, disable the Service in Director, copy the Preview lines in an *.conf file on the master and add the the
command_endpointline. And I write an comment in the disabled service, that other know why they can see the service in dashboard.
Thank you, @khmuth.
Right, so I attempted essentially the same thing by redefining my template Service and object Service as a static conf file in the /etc/icinga2/zones.d/<satellite> directory from my master, and I see that this synced to my satellite. But then my satellite would not apply the config because the host that I was attempting to apply this on was not found on that satellite. This is because all my hosts belong to a different zone cluster and only get synced to those endpoints.
To get this to work, I had to also manually re-define the host on my satellite in /etc/icinga2/conf.d/hosts.conf, and then sync applies. The problem with this is that my hosts list is dynamic and constantly changing--as I'm using Import/Sync automation to maintain this--and my satellites are hard to connect to, so I can't keep all my satellite configs updated manually this way.
Did you also need to define your object Host config manually on the satellite for this to work? I am wondering how I can get Director to sync its host config to this satellite, in addition to the satellites in the zone that are currently defined in Director and being synced to.
We have 2 Linux icinga in a zone as cluster which eare executing the most checks (snmp and all net based checks) and one windows wich executes only some spezilal (powershell) checks for the whole windows world. So we need to spezify the endpoint only for some check templates. In this szenario the patch from #1817 works perfect. We like to see the Patch applied ..
Hello, is there any news about the possibility to "Allow user to specify command_endpoint" in Director ?
