Hello,
I think you must separate the client support and server support in the Centreon ecosystem.
As we don’t need the support for installing the server part of Centreon early on new distribution releases
We need it as soon as possible for monitoring hosts. Because that is the goal on a monitoring solution.
As today , 3 months after Debian 13 release and 6 month after the RedHat 10 release, we can’t monitor efficiently theses hosts.
How can I say to customers that they will not be monitored because Centreon is unable to support majors OS at their release and event months after ?
CMA is not ready for production (too young, features are missing, new tcp ports, new security mechanism, changing enterprise way to do are long path.), so we can't deploy it yet.
You must ensure a period of transition when changing this type of components, by still providing the previous agents and the new one. Both on current OS releases.
So we need to be able to do it with the current tools like NRPE4
https://docs.centreon.com/pp/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4/
The fall back on SNMP is not a viable solution as their is only basic monitoring available.
We can say the same for NSclient for Windows, until CMA is really finished and some times as gone to let users migrate their process and and adapt their configuration, you must maintain it .
NSClient++ is still maintained and is at version 0.10.8 at time of writing, far away of the 0.5 that is packed by Centreon, and it contain numerous security (and features) enhancements :
I hope that Centreon will listen to users need, as we use it to delivers a service to others .