Recently active topics

Every month, Centreon extends its monitoring connector catalog and implements new ones, allowing you to connect your IT monitoring with more ITOps tools.The result: increased visibility and business observability capabilities. We also offer enhancements and fixes on existing connectors. Here is the latest news on your best allies: our monitoring connectors!This May update includes a lot of enhancements and bug fixes, as well as three new connectors : MessPC Ethernetbox SNMP, Rubrik Security Cloud GraphQL API and Westermo Standard SNMP . More details on this month’s monitoring connectors can be found in the release note.Would you like to contribute or suggest improvements? Join us on The Watch or GitHub, where you can also show your support by giving us a star.Additionally, feel free to participate in discussions about plugins and connectors (monitoring packs, Plugin Packs) right here on The Watch.See you next month for more new features!

Hello,Since my last upgrade to 24.10.12, some of my graph’s legends are broken.the metrics are correctly named, but the graphs legend shows “default” instead of metric name.for example : performance data and the graph is : graph legendin parameters > data, metrics name are OK for this service. Any idea how to fix this ?

Bonjour,Nous utilisons Centreon 25.10 sur des serveurs RHEL 9.6 avec le Centreon Monitoring Agent, CMA, pour superviser des serveurs Windows en mode push.Nous utilisons le service template Windows CMA suivant :OS-Windows-Services-Auto-Centreon-Monitoring-Agent-customL’objectif de ce contrôle est de superviser les services Windows configurés en démarrage automatique et actuellement arrêtés.Le service est configuré avec les macros suivantes :STARTAUTO = trueFILTERNAME = .*FILTERDISPLAY = .*SERVICE_TYPE = serviceSTART_TYPE = autoCRITICALSTATE = stoppedMalgré la valeur SERVICE_TYPE=service, le contrôle remonte plusieurs Windows Kernel Drivers comme des services arrêtés.Exemple de retour d’alerte :CRITICAL: services: 4 stopped, 132 runningCRITICAL: dam is stoppedCRITICAL: sacdrv is stoppedCRITICAL: SentinelELAM is stoppedCRITICAL: WdBoot is stoppedSur le serveur Windows, ces objets ne sont pas des services Windows classiques visibles dans services.msc. Ce sont des Kernel Drivers.Vérificatio

Hi,I want to install centreon with this configuration : Centreon server with centreon-central Database on remote mariadb serverAll are in Debian 12.For the centreon central, the install is : apt updateapt upgradeapt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curlip aapt updateapt upgradeapt autoremoveecho "deb https://packages.sury.org/php/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/sury-php.listwget -O- https://packages.sury.org/php/apt.gpg | gpg --dearmor | tee /etc/apt/trusted.gpg.d/php.gpg > /dev/null 2>&1echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.listecho "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.listwget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg >

A new update for Centreon web 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-24.04.26

A new update for Centreon collect 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-collect-24.04.19

A new update for Centreon mbi 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-mbi-24.04.15

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon map 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.04.22

A new update for Centreon mbi 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-mbi-24.04.15

Hello,I have a script to verify that the reboot tasks are running properly on certain virtual machines. For most of the VM fleet, this script works, but for three VMs, I’m seeing this message in Centreon. So I logged into those machines and saw that there was indeed a reboot task, and that it had even been executed the night before.Here is the script in question filter=enabled eq 1 and has_run eq 1 and title in ('Shutdown','shutdown','reboot','Reboot')warning=task_status = 'running' and most_recent_run_time < -60mcritical=task_status not in ('running') and exit_code > 0perf-config=*(ignored:true)show-all Does anyone know why the script does not recognize the reboot task? Best regards,

Hello everyone, I'm having an issue—apparently a communication problem—between my two collectors and my central server. After investigating and conducting extensive research, particularly in the logs, I'm seeing errors when reading the socket data coming from the poller's IP. Here's an excerpt:Central:central-broker-master.logPoller 1:centengine.log For your information, the operating systems are AlmaLinux 8 for the central server and AlmaLinux 9 for the pollers. I installed the latest updates on 25.10.25 Could you help me resolve this issue and let me know if there are any similar cases currently? Thank you.

Hi,Yesterday, i finished my Centreon configuration, as the last ‘job’ i customized the login page.Tobay i opened my Centreon, and it was the original centreon page, not my customization.When i go to the customization i got this now : Nothing was change, no update, no rebot, nothing, i simply closed the interface yesterday @20h45 and open it today @14h145 … Somesone got an idea ? Thanks 

Bonjour, Nous disposons d’une Licence On Prem Business et je souhaiterais rattacher ce compte à cette souscription. comment faire?

Bonjour j’ai une version open source de centreon donc aucune licence payante. Cependant j’aurai aimé utilisé le CMA. Cependant dans la doc technique il est indiqué qu’il faut installer les connecteurs de supervisions qui fourniront les modèles pour les hôtes. Mais je n’y ai donc pas accès. Il y a t-il une autre possibilité ?Merci d’avance !

Bonjour,Depuis que j’ai migré vers la version 25.10.5, je suis obligé de redémarrer mon collecteur tous les jours.Le matin je me connecte et le collecteur semble tourner mais nb de machines : 0 et sur la ligne je retrouve la date de la dernière mise à jour de mon collecteur sur fond Orange.Je redémarre mon collecteur et tout se remet à jour naturellement...Comment puis-je outrepasser cette opération qui n’était pas nécessaire sur la version précédente. Il doit y avoir un paramètre qui bloque l’uptime du collecteur.Merci pour vos retoursBonne journée