Centreon Infra Monitoring

Hello,I have configured the Centreon Monitoring Agent (CMA) for my Windows server.However, when I try to create a host in Centreon and assign the host template OS-Windows-Centreon-Monitoring-Agent-custom, this template does not appear in the host creation form.The template is present and visible in Configuration > Hosts > Templates, but it is not available in the template selection list when creating or editing a host.I am using Centreon 24.10.26 and I do not have a commercial license installed.Has anyone encountered this issue before or knows why this template is not available for host assignment?Thank you for your help.

Background:This is not an App Registration. The requirement relates to an Enterprise Application configured with Single Sign-On (SSO) using SAML. This SAML SSO uses a signing certificate with an expiry date. We would like to track this expiry date in Centreon so that we can plan for renewal and avoid any service disruption.Questions:Is there a plugin pack, connector, or Centreon monitoring method that allows us to retrieve the expiry date of this certificate? If this is not supported natively, is there a method recommended by Centreon for monitoring it, for example via Microsoft Graph, an API, or a custom script? If specific development is required, could you confirm the most suitable approach for integrating this properly into Centreon?We would also be

Hi community,I followed the official installation guide https://docs.centreon.com/fr/docs/24.10/installation/installation-of-a-central-server/using-packages/ for Debian 12 (MariaDB for SGDB), adhering to it step by step.A post-installation note states: NOTICE: Not enabling PHP 8.2 FPM by default.NOTICE: To enable PHP 8.2 FPM in Apache2 do:NOTICE: a2enmod proxy_fcgi setenvifNOTICE: a2enconf php8.2-fpm Executed the following commands:systemctl daemon-reloada2enmod proxy_fcgi setenvif rewritea2enconf php8.2-fpma2ensite centreon Attempt to connect to the interface via http://<IP>/centreon; the Centreon configuration wizard does not

Bonjour,Notre serveur Windows était supervisé en SNMP, et les sondes étaient OK.Sur ce serveur, nous avons mis en place l’agent CMA et les sondes SNMP oscillent depuis entre OK et UNKNOWN.Est-ce que ces deux modes de supervision cohabitent bien ? Faut-il privilégier CMA ?Merci !

Hello, I am currently monitoring the IP SLA on a Cisco 9300.I am having trouble retrieving the jitter metric.However, this metric is clearly visible on the router side.Could you help me?sudo -u centreon-engine /usr/lib/centreon/plugins//centreon_cisco_standard_snmp.pl --plugin=network::cisco::standard::snmp::plugin --mode=ipsla --hostname=XXX --snmp-version='3'  --snmp-username=XXX  --authprotocol=SHA --authpassphrase=XXX --privprotocol=AES --privpassphrase=XXX--filter-tag='10006'  --warning-CompletionTime=50 --critical-CompletionTime=100  --use-new-perfdataOK: RTT '10006' Status : operation sense is 'ok', Completion Time : 7, Number Over Thresholds : 0 | '10006#completion_time'=7;0:50;0:100;0; '10006#number_over_thresholds'=0;;;; ----    Information on the router side ------------

Bonjour,Sur un Remote Server, l’utilisateur ADMIN, n’a pas tous les menus ! Par Exemple, il n’a pas le menu pour ajouter un nouvel hôte.  Sur le RS, l’ADMIN n’a aucun ACL (sur mon Central, non plus)  Le RS est en 23.04 et Debian 11. Comment sont gérés les menus et comment les donner tous à l’ADMIN ?Merci d’avance por votre secours.

Hello,I am experiencing an issue after upgrading my Centreon server to 25.10.13.EnvironmentCentreon Central: 25.10.13 Centreon Web: 25.10.13 Centreon Broker: 25.10.7 Centreon Engine: 25.10.7 MariaDB: 10.11.18 AlmaLinux 9ProblemAfter exporting the configuration from the Centreon Web interface, the broker configuration file is regenerated and the database password is written as an encrypted value:"db_password": "encrypt::..."When cbd starts, it immediately fails with:No usable encrypted password: Decryption finalization failed: error:1C800064:Provider routines::bad decryptThe broker continuously crashes and is restarted by the watchdog.Investigation performedMariaDB is running correctly. The centreon database account works correctly. Manual connection to centreon_storage

Hello,In some services, the following message appears instead of the command:“Unable to hide passwords in command (Reason: Macro passwords cannot be detected)”Even though there are no password-type macros.The cause is in this file/usr/share/centreon/src/Centreon/Domain/Monitoring/CommandLineTrait.phpLine 153, you must comment this block as follow : // if two macros are glued or separated by spaces, regex cannot detect properly password string/** if (preg_match('/\(\.\*\)\s*\(\.\*\)/', $macroPattern)) { throw MonitoringServiceException::macroPasswordNotDetected(); }**/With this you will have your command line shown as expected , and from my te

Upgrading BI from 23.10 to 24.10 breaks PDF report generation, update removes few required JAVA libraries xmlbeans-2.3.0.jar and dom4j-2.1.4.jar.You can download missing JARs fromhttps://repo1.maven.org/maven2/org/apache/xmlbeans/xmlbeans/2.3.0/xmlbeans-2.3.0.jarhttps://repo1.maven.org/maven2/org/dom4j/dom4j/2.1.4/dom4j-2.1.4.jarCopy them to /usr/share/centreon-bi/bin/cbis_lib/ and report generation should work again.

Hi,Due to the end of support of the release 24.04, I have recently upgraded my Centreon plateform to release 25.10 (I have two separate deployments).But I found an issue on one of my deployments.I’m using regex patterns within my “Custom Macro entries”, and I realized that the “$” sign is not passed anymore to the check command.For example, custom entry configured “xe-0/0/1$” becomes “xe-0/0/1” when it is passed to the check command.I have also realized that this issue appears with the release “25.10.12” and not present in “25.10.11”.Any idea ? I didn’t find the release note of “25.10.12” that could explain a change of behavior how custom macro entries are now handled.ThanksDavid

Hello,I want to fully automate the installation and registration of a poller on the central with Ansible.For RPMs or even transcribing the 'registerServerTopology.sh' script, this is no problem.I even managed to generate via a playbook the 'gorgon' configuration of the poller.On the other hand I cannot manage to transcribe the 'poller wizard' module of the interface. I noticed this was using an internal REST API, but I can't find any info on the subject.The objective of this playbook is to install, configure, and declare the poller without administrator intervention (among other things, restarting the gorgon service on the central and the poller)Thank you for your helpPhilippe

Why this appear in command line ? Is there any solution to show command line or  correct this ?  

Hi,I project to migrate to 25.10 and I install a new server on almalinux 9.6.I’m following the installation from the official documentation, and when I reached the MariaDB installation step, there was a conflict with mysql-common :  Total                                                                                                                                                                                                         13 MB/s | 192 MB     00:14Test de la transactionLa vérification de la transaction a réussi.Lancement de la transaction de testLes paquets téléchargés ont été mis en cache jusqu’à la prochaine transaction réussie.Vous pouvez supprimer les paquets en cache en exécutant « dnf clean packages ».Erreur : Erreur de la transaction de test :  le fichier /usr/share/mysql/charsets/Index.xml entre en conflit avec les tentatives d'installation de mysql-common-8.0.43-1.el9_6.x86_64 et MariaDB-comm

We would like to inform you of an important change regarding our network discovery plugin. Due to the licensing terms associated with NMAP and the end of Centreon's distribution rights for this binary, we will be required to remove the NMAP dependency currently bundled within our Centreon Plugin. While this decision affects current behavior, it is necessary to ensure legal compliance and the long-term sustainability of our solution.This change will take effect with the next Monitoring Connectors release scheduled for June. If you are using the NMAP-based discovery feature, it will no longer work after this update without action on your part (related job in error). To continue using it, you will need to manually install the NMAP package directly on your pollers. This operation remains straightforward and well-documented — NMAP is available in the standard repositories of most Linux distributions.We will support this transition with an update to our official documentatio