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 April update includes a lot of enhancements and bug fixes, as well as three new connectors : Hitachi E Series CMA, Linux Libvirt SSH and Palo Alto firewall API . 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!

The Watch celebrates its 4th anniversary… and brings you giftsIt has now been four years since The Watch has been serving the Centreon user community. Four years of shared experiences, valuable contributions, peer support, and passionate discussions around IT monitoring.To mark this milestone and end the year on a high note, we are thrilled to announce the launch of the The Watch Loyalty Program! A program that rewards your engagementYour actions on The Watch, whether asking a question, posting an answer, liking, voting, etc already allow you to earn points. What’s new as of today is that these points can now be converted into real physical rewards, delivered straight to your home: mugs, backpacks, water bottles, and many other Centreon-branded items. How does it work?It couldn’t be simpler: You are an active member of The Watch. Your actions automatically earn points, visible on your profile or in the community leaderboard. These points are transferred in real time to the The Watc

SymptomsWhen a host is linked to a host category, the update fails with the following error in the logs:  [ERROR] Rollback of 'PartialUpdateHost' transaction {"custom":{"trace":"#0 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHostValidation.php(258): Core\\Host\\Application\\Exception\\HostException::idsDoNotExist()\n#1 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(438): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHostValidation->assertAreValidCategories()\n#2 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(183): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHost->updateHostCategories()\n#3 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(152): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHost->updatePropertiesInTransaction()\n#4 /usr/shar

Hi,After upgrading the agent to 25.0.4 (from 25.0.3) it returns No storage found (filters issue).The default FILTERSTORAGETYPE from 25.0.3 is hrstoragefixeddisk, and seems not to work and need .*Is ths will be fixed,because it is a problem when you update the agent in mass.Thanks 

Est-il possible d’utiliser le magasin d’autorités de certification Windows plutôt que de devoir spécifier un chemin vers un fichier de certificat en dur ?Les autorités de certification étant déjà déployées sur mes serveurs via des GPO, il serait pertinent de pouvoir s’appuyer sur ce mécanisme existant plutôt que de maintenir des fichiers séparés.  Is it possible to use the Windows Certification Authorities store instead of specifying a hard-coded path to a certificate file?Since the certification authorities are already deployed to my servers via Group Policy, it would make sense to leverage this existing mechanism rather than maintaining separate certificate files.

HelloI’m using the database::oracle plugin to replace the old one I was using before.Almost everything works fine, except that it does not find 2 tablespaces, SYSTEM and UNDOTBS1, which were perfectly found by the old plugin :  $ /usr/lib64/nagios/plugins/Poller/check_oracle_health.sh -connect ALIAS --name SYSTEM --username XXXX --password YYY --warning 90 --critical 95 --mode list-tablespacesSYSTEMOK - have fun$ /usr/lib64/nagios/plugins/Poller/check_oracle_health.sh -connect ALIAS --name SYSTEM --username XXXX --password YYYY --warning 90 --critical 95 --mode tablespace-usageOK - tbs SYSTEM usage is 11.05% | 'tbs_system_usage_pct'=11.05%;90;95 'tbs_system_usage'=565MB;4608;4864;0;5120 'tbs_system_alloc'=632MB;;;0;5120Unfortunately, with the official oracle plugin, it’s not found :  $ /usr/lib/centreon/plugins//centreon_oracle.pl --plugin=database::oracle::plugin --hostname 1.2.3.4 --port 1524 --servicename SID--username XXXX--password YYY --mode tablespace-usage --filter-tables

Hello,I’m facing an issue with discovery jobs stuck in Running state on my Centreon platform.Context Multiple discovery jobs configured per poller Providers used: VMware (ESXi & VM discovery, ~20 jobs with filters) AWX (2 jobs: pre-prod and prod) Pollers are sized according to Centreon recommendations Jobs are scheduled sequentially with intervals, running once per day IssueRecently, some discovery jobs are getting stuck in Running state indefinitely. On the central server, I get errors indicating that the job cannot be launched because it is already in Running state It is impossible to restart the job from the UI (even after waiting a long time and after restarting gorgoned service ) Checks already performed Reviewed gorgoned logs on central and pollers Checked VMware daemon logs on pollers No explicit errors found explaining the blockage Verified that jobs are not overlapping by design (sequential scheduling) Observations The issue appeared recently (no maj

Voici une version adaptée intégrant ce contexte : Bonjour à tous,Nous supervisons actuellement des conteneurs OpenVZ avec Centreon.Nous disposons d’un ancien plugin “fait maison” qui permet de contrôler l’état des conteneurs (notamment la partie démarrage), mais il commence à dater et nous souhaitons savoir s’il existe aujourd’hui une méthode plus standard / officielle pour superviser correctement cet aspect.Notre besoin est de : Détecter un échec de démarrage d’un conteneur Vérifier que le conteneur est réellement en état running Disposer d’un statut clair et fiable dans Centreon (OK / CRITICAL si le conteneur n’est pas démarré) Éviter de maintenir un script custom si une solution packagée existe Nous n’avons pas trouvé de plugin officiel Centreon Plugin Pack dédié à OpenVZ pour cette vérification spécifique.Existe-t-il : Un plugin officiel Centreon compatible OpenVZ ? Une bonne pratique recommandée (via SNMP, agent, API, commande système côté hôte) ? Un mode opératoire vali

Bonjour,J’ai une question par rapport à l’Activité métiers (Business Activity). Récemment, on m’a demandé de créer des activités métiers pour mes serveurs, mes applications hébergées. Cependant, je l’ai créé que depuis la semaine dernière. Cependant, les applications et les serveurs existaient depuis pas mal d’année. Par contre, quand je génère un rapport pour mon activité métier, il n’affiche que les valeurs à partir de la création de l’activité métier pour mes serveurs et mes applications. Est-ce normal? Comment je peux faire pour que ce rapport prend toute l’historique de mes serveurs et de mes applications? Ou ce n’est pas du tout possible?Aussi, j’avais déjà quelques activités métiers en place depuis pas mal d’année. Et j’ai modifié les plages d’horaire de rapport de 24x7 en heures ouvrées de 8h à 20h et aussi supprimer quelques indicateurs non utiles à mes rapports. Est-ce que j’aurai une réécriture de mes historique d’activités métiers dans ce cas là, ou bien c’est comme si je r

Hi,in my Centreon on premise version 25.10.9, if i go the page:Configuration → Connectors → Monitoring Connectorsand i click to the botton “Update all”, i get this error: “An error occured while installing the following monitoring connector :+ base-genericReason: Authentication failed, company not foundSo the following monitoring connector were not processed+ base-generic” while on file /var/log/centreon/license-manager.log a this line appears [2026-04-07T15:35:24+02:00] ERROR : 0|0|[RestUnauthorizedException] https://api.imp.centreon.com/v2/auth/instance : Authentication failed, company not found | {"custom":null,"exception":null,"default":{"request_infos":{"uri":"/centreon/api/internal.php?object=centreon_pp_manager_pluginpack&action=updateAllPluginPacks","http_method":"GET","server":"10.40.11.150"}}} The license is an IT100This issue happened after the upgrade from version 24.* to 25.* How can i fix this issue?     

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

A new update for Centreon gorgone 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-gorgone-24.10.13

since middle on weekend all service usinf esx8 api popup same error:UNKNOWN: no data for resource host-709473 counter mem.capacity.usable.HOST at the moment. - no data for resource host-709473 counter mem.consumed.vms.HOST at the moment. - get_esx_stats function failed to retrieve statsThe counter mem.capacity.usable.HOST was not recorded for resource host-709473 before. It will now (creating acq_spec).The counter mem.consumed.vms.HOST was not recorded for resource host-709473 before. It will now (creating acq_spec). in debug on poller:== Info: We are completely uploaded and fine=> Recv header: HTTP/2 500=> Recv header: date: Mon, 09 Mar 2026 14:24:12 GMT=> Recv header: content-type: application/json=> Recv header: x-envoy-upstream-service-time: 13=> Recv header: vary: Accept-Encoding=> Recv header:=> Recv data: {"messages":[{"args":[],"default_message":"Unable to create Acquisition Spec due to conflict at row: `375`","localized":"Unable to create Acquisition Spec

Hello, just here to share to the community an issue that i encountered, the underlying issue, and how it can be resovled.This happened on a quite heavily loaded central server (poller included), and my end users reported receiving load of emails alerts regularly, but during bursts of a few minutes.After investigating the commands failing, there was nothing to correleate them, any service could fail, and all failed with the same output: “Execute command failed”. Something strange was at work here.After going more in the logs, especially centreon-engine logs, i find it. “Too many open files”. Here is the issue.At first i supposed there was permissions issues or something, but this is irrelevent as all can happend to any commands usually working fine. So i dig deeper on the internet, and here i find it, the Linux File Descriptor Limit. cyberciti.biz - linux increase the maximum number of open files . This limit by default is around 1024. I then do a quickls /proc/[centengine_pid]/fs/*and

Following a recent update of the plugins on my Centreon servers, I am facing issues with the Fortinet plugin, specifically impacting the SD-WAN and VPN services. Could you please assist me in resolving this issue? Unknown option: include-vdomain at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 4524.  Unknown option: include-vdom at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 4524.

Hello,Somebody know a fresh project for have a notification per mail with html ?I see GitHub - mcinquin/centreon-notifications: New notifications for Centreon but it’s 9 years old.HTML/formatted Notification | Community stil in the backlog apparently ?Regards,B’