Easier ways to configure CMA

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

2. 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.

Hi ​@mikail ,

1. i send you a meet proposal to discuss that

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 ?  →  Yes, that’s it

Hello ​@fmattes ,

1. For this point, we have decided to go to fully use the poller-initiated connection (after your advice on the meeting we had the 3rd November) so I don’t know if having a new meeting is still relevant.
2. For the configuration, I have created an agent configuration per poller. We first tried to use one config for every poller but it was bugged : to illustrate this the line “broker_module=/usr/lib64/centreon-engine/libopentelemetry.so” was not present in the centengine configuration file for the pollers. Besides, if a host changes poller, two poller tries to connect to its agent and the monitoring gets down. To avoid this, I have written a script that for each host (with agent) fetches its ID, the poller ID it is affected to and add it in the right configuration through the API. It works for now but the configuration through the hosts menu or hosts endpoint in the API will be very helpful to us and we are looking forward to it.