Hello
I’m planning to work with the CMA agent in the mode “poller connects to the Agent”
I have trouble understaning what is the “link” between the “host” in the CMA Configuration, the “Host ip address” in the otl_server.json file, the “host” and the “alias” in the centreon configuration.
more globally, I have an issue with the need to use a hostname in the agent configuration, especially in the mode poller contact the agent, and the way our setup is done. as a MSP, I deploy servers for client, monitoring agent (nsclient or snmp) are already included, and the need for a hostname is not necessary
on my centreon config, I have multiple serveur with identical name, (srv01 on multiple client), so I don’t really use the real hostname except in the Aliases, all the “host name” in my centreon are prefixed with a client code, then the hostname ‘XXX_SRV01’ for example)
the only thing I would consider an unique identifier would be that on a poller there are no duplicated addresses, so the ip address of a host is always unique on a poller. (but I have multiple poller with client using the same subnet)
I have made a few try in modifying the values here
and here
if the value do not match the agent has no schedule working and the check are pendings.
if the value match, the check are working.
this leads me to believe the hostname from the agent is the key, and this is causing me some issues for the future, what happen if host have the same name, and how can I manage that with my centreon host names being all different from the client hostname
is there a way to make that hostname matching disappear completely as a concept? maybe to make it so the agent or the poller generate a unique id that is then used? (and not at setup time, as cloning and templating VM could be an issue if the id is generated at setup time)
in the current centreon behaviour the agent is nameless, the poller talks to an address, ip or dns, but the poller handles the ID of that host because the host address is unique for that poller and the “active check” leaves no room for guessing the host
I would l like to see a similar behaviour, but I don’t know how/if it is possible.