Infra Monitoring Data collection

HelloWhen using service template :OS-Linux-Cpu-Centreon-Monitoring-Agent -> Generic-Passive-CMA-Service-custom -> Generic-Passive-CMA-Service check command is set to :/usr/lib/centreon/plugins//centreon_linux_local.pl --plugin='os::linux::local::plugin' --mode='cpu'  --warning-core='' --critical-core='' --warning-average='' --critical-average='' --statefile-dir=''   but when --statefile-dir=’’, plugin tries to write in /, which results in :     UNKNOWN: Cannot write statefile '/cache_linux_local_me_cpu_a181a603769c1f98ad927e7367c7aa51'. Need write/exec permissions on directory. => the flag --statefile-dir=’’ should be removed from the default command / template

Hello,With Bind 9.20.22 when I try to check the memory-usage, I got no value and an exit in Ok state :centreon_plugins.pl --plugin apps::bind9::web::plugin --hostname 10.128.112.211 --port 8080 --url-path /xml/v3/mem --mode memory-usageOK: usage : skipped (no value(s))The value’s name for the total has changed in “apps/bind9/web/custom/api.pm”Line 192 :< if ($name eq 'TotalUse') {---> if ($name eq 'Malloced') {But there is still the problem with the output code and message if the value is not found. It should exit in Unknown.

Hello,I was wondering why there is so many differences between the NRPE for Debian and for RedHat, Debian user : centreon-engine (?!)RedHat user : nrpe Debian config : /etc/nrpe/centreon-nrpe4.cfgRedHat config :/etc/nagios/nrpe.cfgBy default, the only difference between these disto are the user used to run the binaryRedHat : nrpeDebian : nagiosTheses new inconsistencies are painful to manage, perhaps the Debian package build by Centreon can set the same user as under RedHat The last thing I don’t understand is why you asked to add this repository for Debian https://packages.sury.org/php Which template needs PHP on a remote server monitored via NRPE ? 

Hello I’am checking the sensor component but I have criticals when ethernet is down and as no amperes which is normal. Sensor 'Ethernet1/26 Lane 1 Transceiver Bias Current Sensor/300044004' is 0 A  How can I filter this I tried several ways with no result.  --filter='(?!.*is.*0.*A.*)'--filter='(?!.*is.*0.*)'-filter='^(?!.*is.*0.*)'--filter-perfdata-adv='not (%(value) == 0)'--filter-perfdata-adv='not (%(label) !~ "sensors.amperes.*")'--filter-perfdata-adv='not (%(label) =~ "sensors.amperes.*")'--filter-perfdata-adv='not (%(label) == "sensors.amperes.*")'

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

Hi!I’m trying to follow the tutorialto implement monitoring of SAP SCC. Two issues:HTTP basic authentication: it’s not clear from the tutorial how to get a plain simple HTTP basic auth. Took me hour to figure out (use the source, Luke!) that you just need to pass ‘basic’ like this: "authorization": {"basic": 1,"username": "%(constants.username)","password": "%(constants.password)"}, I would add it to the original post, but the comments are locked. Please add it, so people save a lot of time. Path depth. SAP will respond with a JSON of this type: { "subaccounts": [ { "description": "SAP BAS", "displayName": "SAP BAS", "tunnel": { "state": "Connected", "connectedSinceTimeStamp": 1720773876375, "connections": 0, "applicationConnections": [], "serviceChannels": [], "subaccountCertificate": { "notAfterTimeStamp": 1749540416000, "notBeforeTimeStamp": 1718000816000, "subjectDN": "CN=B0CADA20E31311EBBF8AD

Hi,I encounter this strange behavior for both AIX 6 and AIX 7, for all the hosts I tested: [centreon-engine@poller ~]$ /usr/lib/centreon/plugins//centreon_aix_snmp.pl --plugin=os::aix::snmp::plugin --mode=time --hostname=aixserver --snmp-version='2c' --snmp-community='xxx' --warning-offset='-5:5' --critical-offset='-10:10' --debugCRITICAL: Time offset 3600 second(s): Local Time : 2024-11-22T13:14:29 (UTC) | 'offset'=3600s;-5:5;-10:10;;.1.3.6.1.2.1.25.1.2.0 = ▒[centreon-engine@poller ~]$ snmpget -cxxx -v2c aixserver .1.3.6.1.2.1.25.1.2.0 HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2024-11-22,13:14:51.0[centreon-engine@poller ~]$ /usr/lib/centreon/plugins//centreon_aix_snmp.pl --plugin=os::aix::snmp::plugin --mode=time --hostname=aixserver --snmp-version='2c' --snmp-community='xxx' --warning-offset='-5:5' --critical-offset='-10:10' --debug | cat -ACRITICAL: Time offset 3600 second(s): Local Time : 2024-11-

Hello,I am using a homemade service template similar to  App-Protocol-HTTP-Json-Content to get information from a database and value the number of users connected to a wireless network profil / SSID. I am confused by the range definition which seems not demonstrating what the following documentations annouce :https://docs.centreon.com/fr/docs/monitoring/metrics/ https://nagios-plugins.org/doc/guidelines.html#THRESHOLDFORMAT I want the service to be in WARNING state if element_1 = 0, and CRITICAL if element_1 < 40. Starting with the WARNING, here are my test results (for the purpose of the test I am replacing 0 and 40 by the output of the service the simulate and NOK case) :Definition or range for WARNING seems ok sometimes, nok others : [centreon-engine@mypoller ~]$ /usr/lib/centreon/plugins/centreon_protocol_http.pl --plugin=apps::protocols::http::plugin --mode=json-content --hostname=[Hostname] --proto='https' --port='8181' --cacert-file='/etc/pki/tls/certs/ca-bundle.crt' --urlp

Hi,Since the NSClient++ project has been on a long break (from april 2018 and november 2023) we have never included its releases in our continuous integration processes. But since then, the project show an impressive level of activity.As we have been very busy doig a lot of other things, we have fallen far behind on this updating the base version of NSClient++ used for our builds.We’re currently trying to bridge this gap and given the wide number of changes, we may expect some regressions.Please feel welcome to use this pre-release and give us feedback here!Here are the known issues (I’ll update them as they’ll be found):The old authentication (using --legacy-password and no login) does not seem to work anymore. Since it’s not a good practice, you’re invited to switch to  --username and --password. NB: the apps::nsclient::restapi::plugin needs this commit to handle this authentication process. 

Bonjour,Nous avons actuellement une sonde du genre /usr/lib/centreon/plugins/centreon_protocol_http.pl --plugin=apps::protocols::http::plugin --mode=expected-content --hostname=hostname --proto='https' --port='443' --urlpath='/api/' --expected-string='"status":"pass"' --ssl-opt="SSL_verify_mode => SSL_VERIFY_NONE"OK: HTTP test(s) | 'size'=29B;;;0; 'time'=0.538s;;;0; /usr/lib/centreon/plugins/centreon_protocol_http.pl \  --plugin=apps::protocols::http::plugin \  --mode=json-content \  --hostname=url \  --proto='https' --port='443' \  --urlpath='/api' \  --header='Accept: application/json' \  --lookup='$.status' \  --threshold-value='values' \  --warning-string='' \  --critical-string='^(?!pass$)' \  --ssl-opt='SSL_verify_mode => SSL_VERIFY_NONE'OK: 1 element(s) found | 'count'=1;;;0; 'time'=0.599s;;;0;curl -s  https://url<?xml version="1.0" encoding="UTF-8"?><root><status>pass</status><version>0.10</version></root>  Nous aimerions utiliser

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 

2025-07-20 03:22:57 - DEBUG - => Send data: {"security":{"credentials":{"login":"centreon-gorgone","password":"Jxx5@yyT8!My"}}}Logs, even at debug level should not leak credential of a system user. This log file is by default world readable (/var/log/centreon-gorgone/gorgoned.log).

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

hi, i work with the plugin centreon vmware.in test my result is OK with a vcenter, /usr/lib/centreon/plugins/centreon_vmware_connector_client.pl --plugin=apps::vmware::connector::plugin --mode=swap-vm -custommode=connector --connector-hostname='localhost'     --connector-port='5700' --container='***********’ i have installed the connector in the same os, but in a highest release (centos 7.4 vs centos 7.9) , the same command return : UNKNOWN: Cannot encode resultwith debug :{ "code": -1, "short_message": "Cannot encode result" }the pb is not the .pm, this is ok on the test platform , and when i ask it with curl in the prod server , it’s ok ...is anyone has (or had) the same problem and have resolved it ? do you have the same problem with another plugin ? 

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] -class- host discovery - cannot get platform versions - Login error [code: '401'] [message: 'Unauthorized']central-gorgone version

I would like to see the SLA availability level for each host in my host group over a period of one year. Which metric and widget on the dashboards would allow me to find this out?Thank you in advance!

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,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 current OS releases.So we need to be able to do it with the current tools like NRPE4https://docs.ce

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.