Skip to main content

Hello,

Could it be possible to indicate several endpoints in the configuration of CMA ? As we plan to migrate from SNMP to the agent for our Linux servers, it would mean that for each server we have to indicate the right poller to which the host is affected, which complicates our task. Besides, it can causes issues if the host is moved to another poller.

In the current state, we plan to use the reverse connection, where the poller initiate the connection to the agent, but even so, we have to configure each host in the agent configuration on Centreon. Using the API, we do not have simple way to add hosts, using the PUT method writes on the whole configuration. Meaning that we have to indicate every host in the API request when we want to add a host. And we have to indicate the ID of the host, simply indicating its name is not enough.

Even if we can use the default connection (agent → poller), we’ll have to use this method for our servers in DMZ.

To summarize, is it possible to add several endpoints in the centagent.json configuration file and have an easier way to add hosts in the reverse connection type configuration for CMA ?

 

Thank you in advance.

 

 

New→Planned

HI,

There are, indeed, 2 ideas in 1.

  1. Multiple endpoints in agent configuration (Host)

I understand this pain-point : “Besides, it can causes issues if the host is moved to another poller.”

But i don’t understand this one : “As we plan to migrate from SNMP to the agent for our Linux servers, it would mean that for each server we have to indicate the right poller to which the host is affected, which complicates our task.” You can put endpoint in any automated deployment, when you put CMA paremeters (file or registry depending on the OS).

 

Could you explain more  this painpoint ? thanks

 

  1. Ease hosts configuration for Poller-initiated connection

We are currently working on the following use case, would it match with your needs ?

When creating the poller, create (automatically?) an empty host AC, which will carry a default token replicated on any new host added (in 95% of cases it is always the same token).

When creating the host (UI/API), associate (unit/massive change) this host with a poller-initiated AC.

Hello ​@fmattes,

Thank you for your quick answer. To answer you :

  1. My point was, as the hosts are already monitored - and as I understand the functioning of CMA, we have to export the list of the hosts with the corresponding poller, so when we deploy the CMA on the host we have to indicate the poller currently used in monitoring as an endpoint. That would mean that we couldn’t deploy the same configuration for each of our server and we have a hundreds of them.
     
  2. I’m not sure to understand the use case. Does “associate (unit/massive change) this host with a poller-initiated AC” mean that we could massively affect hosts in to an agent configuration in the “Configuration >  Hosts” menu ? If this is the case this will indeed be very helpful for us. If this is only at the creation of host/poller, then it won’t as we have already created these.

Regards.

Terms & ConditionsCookie settingsAccessibility statement