Infra Monitoring Data collection

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 --hostname='vcenter.mycompany.fr' --port='443' --proto='https' --esx-name='esx1.myc

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     India: https://api.meraki.in/api/v1     United States FedRAMP: https://api.gov-meraki.com/api/v1Please refer to Meraki API documentation Cisco Meraki Base URI and our October 2025 release note for more details.

 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

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.

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:Thank you!

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 certificates, mais je ne vois pas comment les intégrer ou activer ce mode dans le plugin centreon_windows_wsman. ❓ Ce que je cherche : Des conseils ou un exemple pour ajouter un nouveau mode au plugin centreon_windows_wsman. De

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

Hello,I need to monitor my new SDWAN platform, PaloAlto ION SDWAN.Could you tell me if you have something about this solution ?I can get you MIB or some other stuff.Thank by advanceBest RegardsYohan

Hello all,I use the plugin for postgresql and on the dtailed ouput, i have the message “OK: SQL statement result : 1.”.I would to change this out in “OK: SQL statement result : Primary.” for example, it will depend of the value.Thank you in advance,Hassane

Hello,I'm using the "OS-Windows-disk-Global-SNMP" plugin to monitor the remaining free space on my disks, but I've noticed that the detection stops at 2 TB.Have you already noticed this issue on your monitors?Sincerely,Eric

Apologies if this is a duplicate. I could not find an existing similar issue.centreon V24.10plugin nrpe4 for linux 25.09.0After installing NRPE plugin I tried to use the provided template OS-Linux-File-Date-Generic-NRPE4-custom.I added the service to an existing host and the resulting check command produced was/usr/lib64/nagios/plugins/ -H my_monitored_host -p -t -c check_centreon_plugins -a 'os::linux::local::plugin' 'files-date' ' --files="my_monitored_file" --warning="172800" --critical="259200" --filter-plugin="" --verbose' Which obviously failed for 3 reasons:path to the executable was missing option -t was empty option -p was emptyI created my own check command and service template to have the following check command: /usr/lib64/nagios/plugins/check_nrpe -H my_monitored_host -c check_centreon_plugins -a 'os::linux::local::plugin' 'files-date' ' --files="my_monitored_file" --warning="172800" --critical="259200" --filter-plugin="" --verbose'My monitoring was then OK.Is it

🇬🇧Hello,I’m having an issue with the Bluemind plugin. I’ve tried different “ssh backend” options, but I keep getting errors.With sshcli:UNKNOWN: sshcli backend cannot use ssh password. please use backend plink or libsshAnyway, I mostly use service accounts, so I tried libssh :UNKNOWN: command execution error [exit code: 7]Or if the mode is set to core instead of xmpp :UNKNOWN: Cannot serialize statefile '/var/lib/centreon/centplugins/bluemind_core_***.***.***.***_xxxxxxxxxxxx....'Never mind, I tried plink:UNKNOWN: Command error: Can't exec "plink": Aucun fichier ou dossier de ce type at /usr/lib/centreon/plugins//centreon_bluemind_ssh.pl line 4059. I tested the service account on the Bluemind VM and got a proper response with the curl command specified in the documentation, but nothing works.I just upgraded Centreon to version 24.10 today after upgrading Debian from 11 to 12. We’re using an IT100 license. Thanks Have a nice day --------------------------------------------------------

Hello everyone,We are currently using the following plugin to retrieve all AWS CloudWatch alarms:/usr/lib/centreon/plugins/centreon_aws_cloudwatch_api.pl --plugin=cloud::aws::cloudwatch::plugin --mode=get-alarms --custommode='awscli' --aws-secret-key='***' --aws-access-key='***' --aws-role-arn='' --proxyurl='' --region='sa-east-1' --filter-alarm-name='' --warning-status='%{state_value} =~ /INSUFFICIENT_DATA/i' --critical-status='%{state_value} =~ /ALARM/i' --verbose We have an active alarm, which can be confirmed when using the --debug option. The output indicates that the instance memory has <StateValue>ALARM</StateValue>. However, the final result is:ok: status : skipped (no value(s)) My question is: could this be a potential bug in the plugin?When running the native AWS CLI command:aws cloudwatch describe-alarms --region sa-east-1 --state-value ALARM all active alarms are correctly returned, while the plugin does not display them.Below is the --debug output showing the a