Infra Monitoring Data collection

VMWare 8 connector : First stone

Hello everyone, As part of our project to update our dedicated VMware connectors, we are deploying the foundation of the VMware 8 ESX monitoring connector via REST API this month. This connector is a lightweight version, as it only includes CPU, memory, power and host discovery modes. We have already planned to enhance this connector in the coming months with new modes. It is marked as experimental because, at this stage, we still need to verify its functionality with numerous metrics (as may be the case in certain production environments). Feel free to share your feedback on this and more generally on this connector here. We will keep you informed of progress on this subject.

41719

27 days ago

fmattesCentreonian

published in Infra Monitoring Data collection

Centreon Monitoring Agent Beta is live !

The new Centreon Monitoring Agent is now available in BetaGreat news for all Centreon users! We are thrilled to announce that the new Centreon Monitoring Agent (CMA) is now available in its Beta version. This agent can be installed on both Windows and Linux hosts, providing enhanced flexibility and scalability to your monitoring setups.Install the Agent on your host & set up monitoring checks You just have to follow the guide ! The Monitoring Connectors October release will provide all you need to quickly and easily monitor hosts using the Centreon Monitoring Agent. Enjoy the Centreon Monitoring Agent experience

3194

omercierCentreonian

About Linux SNMP version 3

Dear Watchers,It had been asked for a while, we released it last December: a SNMP version 3 template is provided for Linux in our Monitoring Connectors. The documentation can be found there.I invite you to tell us here as a reply to this post, if you have feedback to give us about it.Does it fit your needs? Is it easy enough to use? Is the documentation clear?Any feedback will be great!Once we judge that the template is satisfying enough given your feedback, we’ll merge it into the Linux SNMP monitoring connector and apply the same method with

3789

benoitpBuilder **

SNClient+ : short review

Hello,I tried SNclient+ and I will share what I found with this short review.My thirst thought is that SNClient+ is mainly for Windows host.s Why ? Because I failed to installed it from Debian 5 to Debian 11 included. The Debian packages are broken on all theses releases, you can’t install it, it will throw an error.The answer from the team was if it’s not working you can try to recompile it from sources.It more sunny on the RedHat side because the RPM is valid (and tested) on RedHat 7 and 9 (I didn't test it on RH8).Also, only a unit for Systemd is included, no Init script.On the Windows side, it’s unclear on which version we could run it.I successfully run it on Windows 2019 but the SNClient+ team don’t give a list of supported OS :https://github.com/ConSol-Monitoring/snclient/issues/48

5234

ltirandCentreonian

Retirement of Office 365 connectors within Microsoft Teams

Hello everyone,Some of you have already seen the information and have already passed it on to us (thanks again for your vigilance and your feedback). Microsoft made this announcement at the beginning of July:Starting August 15th, 2024 we will be removing the Office 365 connectors feature from Microsoft Teams. We recommend Power Automate workflows as the solution to relay information into and out of Teams in a scalable, flexible, and secure way.We will gradually roll out this change in waves:Wave 1 – effective August 15th, 2024: All new Connector creation will be blocked within all clouds Wave 2 – effective October 1st, 2024: All connectors within all clouds will stop working

3204

ltirandCentreonian

Does MQTT mean something to you? And Mosquitto?

Hello everyone,We started working on MQTT and more specifically Mosquitto with the aim of making a new monitoring connector for it. We already have some ideas but we would like to know if any of you are already using Mosquitto and if so for what purpose do you use it? But also your wishes regarding the monitoring of it.

901

omercierCentreonian

What Monitoring Connectors need a SNMP version 3 template?

Dear Watchers,As I said here, we experimented a new SNMP version 3 template for Linux.We are planning to add similar SNMP version 3 templates to other monitoring connectors to make it easier to use SNMP v3 (I agree it's not ideal to use the $_SERVICEEXTRAOPTION$ macro for that) in more contexts.What I'm proposing you here is to answer to my post by giving:The name of the monitoring connector or the host template you'd like to see support SNMP v3 macros. The desired security levels (noAuthNoPriv, authNoPriv, authPriv).Then we'll prioritize the posts that will receive the highest number of "thumbs up" to deliver new templates in the monitoring connectors.Can’t wait for your suggestions!PS: If what you want is a template that do not exist yet as a mo

3875

mgu_flagSteward *

Migrations 22.10 vers 25.10 macro de services non interpretées

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

8113

15 days ago

Stéphane

[Gorgone] Password leaks in debug log

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).

251

16 days ago

yannsSteward *

Error 401 with connector vsphere8

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

1457

27 days ago

dagabardSteward *

UNKNOWN: Cannot encode result error in plugin centreon vmware.

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 ?

601

Cm123Builder **

New poller not communicating properly

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]

282

JsecondSteward **

SLA availability Which Widget ? Which Metric ?

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!

181

zell1234Steward *

Erreur lors l'affichage ou creation des graphs centreon 25.10

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

211

sdouceBuilder **

Host performance are useless ?

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

1148

benoitpBuilder **

Support for monitoring latest Debian and RedHat host with usual tools

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

443

c2s_talanSteward *

Cannot install NRPE4 connector on ALMA Linux 8.10

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.

1125

yannaelSteward *

Support de RHEL10

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.

311

ahartungBuilder *

Ghost- old Host / Perf Data / metric

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

SEBASTIEN97420Steward *

VMWare connector

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

455

perodoSteward *

supervision d'un FortiAp

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

1043

published in Infra Monitoring Data collection

ltirandCentreonian

Cisco Meraki Rest API: Important updateNews

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

340

2 months ago

syrineSteward *

Problem export config to the central server centreon 24.10

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

2 months ago

DenzricafortSteward *

Centreon Palo Alto - Inquiry

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:

333

RedaSteward **

Monitoring Switchs SAN IBM 512B-7

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.

201