Infra Monitoring Data collection

Bonjour à  tous lorsque je veux affiché les graphs des données reçu j’ai ce message d’erreurs sur debian 12 

Is there any configuration to graph ping host performance data .All my are populated with perfdatas ,But i see no graph …Any idea ? 

Hello,We have created new poller with version 24.10.14 which is not communicating with poller.please have a look at below log from poller as well as central server. poller centengine.log2025-12-03T00:19:57.160-05:00] [processing] [error] [912] failover: global error: failover: 'central-module-master-output' cannot connect endpoint.[2025-12-03T00:22:20.519-05:00] [tcp] [error] [912] TCP: could not connect to 10.*.*.*:5669 : Connection timed outand central servergorgone.log2025-12-03 12:44:46 - ERROR - [legacycmd] Cannot process message type 'SENDCBCFGthrowing it away.2025-12-03 12:44:51 - ERROR - [legacycmd] Cannot process message type 'SENDCBCFGthrowing it away.2025-12-03 12:45:21 - ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - Login error [code: '401'] [message: 'Unauthorized']2025-12-03 12:46:21 - ERROR - [autodiscovery]

​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 releasesWe 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 cur

Bonjour,Je viens de migrer mon centreon 22.10 vers 25.10 centos7 vers Debian12. Tout est parfaitement fonctionnel mis à part les macros des services par groupe d’hôtes qui ne sont plus interprétées et non présentes dans le fichier /etc/centreon-engine/services.cfgEn revanche les macros des services par hôtes et les macros d’hôtes sont elles bien interprétées et présentes dans les fichiers de config.Est ce qu’il y a un changement dans la prise en charge de ses macros ?J’ai essayé de passer par des templates pour mettre les macros mais comme se sont des templates lées à des services de groupes d’hôtes le résultat est le même. Merci pour vos retours 

I am following the documentation: https://docs.centreon.com/pp/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4/ But when I try to install the connector on ALMA Linux 8.10 with the following command:dnf install centreon-pack-operatingsystems-linux-nrpe4 I get the following error:No match for argument: centreon-pack-operatingsystems-linux-nrpe4Error: Unable to find a match: centreon-pack-operatingsystems-linux-nrpe4  PS: I am trying to monitor Linux RHEL services launched with systemdThank you for your help.Regards.

Bonjour,Est-ce que le support de RHEL 10 est prévue? Au moins pour la partie plugins? Pour le moment, il n’y a pas de repository disponible dans cette version.Merci,Yannaël G.

How can i delete old Hosts / Metrics / Perfdata from the database ? I delete a lot of host , i can see the Hosts.. but  This host no longer exists in Centreon configuration. Please reload the configuration. how can i detect all ghost Hosts / Dand the all “old” data from the database TThanks    

Has anyone experienced VMware ESX / vCenter plugins crashing since upgrading to version 25.10?

Hello everyone, We updated our ESXi to version 8.So I'm trying to configure the new VSphere8 connector without success.I created a dedicated account on vCenter for monitoring.This account is functional since the "host-status" mode is working correctly:/usr/lib/centreon/plugins/centreon_vmware8_esx_restapi.pl --plugin=apps::vmware::vsphere8::esx::plugin --mode=host-status --hostname='vcenter.mycompany.fr' --port='443' --proto='https' --esx-id='host-1234' --username='supervision-centreon@vsphere.local' --password='XXXXXXXXXXXX' OK: Host 'esx1.mycompany.fr', id: 'host-1234': power state is POWERED_ON, connection state is CONNECTEDI can also connect to vCenter via the web and view the characteristics of my ESXi and VMs.I'm having a problem with all other services associated with this connector:/usr/lib/centreon/plugins/centreon_vmware8_esx_restapi.pl --plugin=apps::vmware::vsphere8::esx::plugin --mode=power

Bonjour,Connaissez-vous un moyen de superviser un FortiAP avec Centreon ?. Merci d’avance pour votre aide.

Cisco Meraki recently announced a significant change to base Uniform Resource Identifiers (URIs) as part of their continuous security hardening processes, requests to unsupported base URIs will start to fail on November 17, 2025. This means that for the Cisco Meraki Rest API connector, using the default value api.meraki.com for your hostname will work for most of the world. However, for organizations hosted in the following country dashboards, you need to override this value and specify the respective base URI instead:    Canada: https://api.meraki.ca/api/v1     China: https://api.meraki.cn/api/v1 

 Good morning,Can you help me please resolve this problem, I am currently facing an issue after migrating from Centreon 21.10 (deployed on CentOS 7) to Centreon 24.10 (on Debian 12). After exporting the configuration, changes apply correctly to the pollers, but not to the central server. The changes only take effect when I restart the Centengine.I found this error in gorgoned.log : [legacycmd] Event: [ack] [] {"data":{"error":"unknown_action","message":"action 'ACTIONENGINE' is unknown"},"code":1}Thank you

Hi Centreon Team,Good Day! I'd like to inquire about the percentage computation on PALO ALTO Firewall interfaces. We're seeing an issue with outputs surpassing 100%. Is there any way we can receive similar, if not identical, data from the NetSec team? Please see the data below.Outputs in Centreon using the new paloalto plugin:CRITICAL: Interface 'ethernet1/3' Packets In Error : 531313.88% (11832360 on 2227) | 'packets_discard_in'=0.00%;;;0;100 'packets_error_in'=531313.88%;0:90;0:95;0;100 'packets_discard_out'=0.00%;;;0;100 'packets_error_out'=0.00%;0:90;0:95;0;100Interface 'ethernet1/3' Packets In Discard : 0.00% (0 on 2227), Packets In Error : 531313.88% (11832360 on 2227), Packets Out Discard : 0.00% (0 on 2094), Packets Out Error : 0.00% (0 on 2094)Data coming from the NetSec Team:

Hello,We are currently overhauling our SAN switch fleet;The new ones are IBM 512B-7 SAN Switches, and we can't find dedicated connectors for this type of equipment, nor can other IBM SAN switch connectors monitor FC (Fiber Channel) ports.This is very critical for us, and we would like to know how we can proceed urgently, please.

👋 Bonjour à tous,Je suis en train de travailler avec le plugin Centreon centreon_windows_wsman pour superviser des machines Windows via WSMAN, et j’aimerais ajouter un mode personnalisé permettant de surveiller les certificats installés sur le système, notamment leur date d’expiration. 🎯 Objectif : Pouvoir générer des alertes lorsque des certificats approchent de leur date d’expiration, afin d’éviter les interruptions de service. 🔧 Ce que j’ai déjà :Le plugin fonctionne bien pour les modes standards comme cpu, memory, etc. En explorant le dépôt GitHub, j’ai vu que des fichiers liés aux certificats existent : src/os/windows/local/mode/certificates.pm src/centreon/common/powershell/windows/certificates.pm Ces fichiers semblent déjà poser les bases d’un mode certific

Do someone managed to make it worked, the allocated-pods metric return me the following : OK: All nodes status are okNode 'cpklp001.ad.curia.europa.eu' Status is 'Ready', New Pods Schedulable : true - allocated-pods : skipped (no value(s))i have the folowing command :/usr/lib/centreon/plugins/centreon_prometheus_kubernetes_api.pl --plugin=cloud::prometheus::direct::kubernetes::plugin --mode=node-status --hostname=example  --url-path='/api/v1'  --port='443' --proto='https' --node='node=~".*"' --warning-status='' --critical-status='%\{status\} !~ /Ready/ || %\{schedulable\} =~ /false/' --warning-allocated-pods='' --critical-allocated-pods='' --units='' --verbose 

Greetings ! I have a cluster using Ceph that I would like to monitor.I set up the restful ceph api like this : ceph config set mgr mgr/restful/server_port 8443ceph config set mgr mgr/restful/server_addr 0.0.0.0ceph restful create-self-signed-certceph restful create-key centreon #demo userHowever, after setting up the host like this : I have the following error : UNKNOWN: 405 Method Not AllowedIt seems the collector is trying to auth via a post, however it seems the restful api doesn’t auth like this now (I am on Ceph 19.2.3 Squid right now). Is this an issue on my part (I chose the wrong API, maybe ?) or is there a fix to do ? Thanks in advance