Infra Monitoring Data collection

Vulnerability Management: What if Centreon could track your CVEs in real-time?

Hello Watchers!At Centreon, we are constantly exploring new ways to make your IT operations smoother and more insightful. Today, we’re looking into a strategic topic and we’d love to get your thoughts: The convergence of Monitoring and Cybersecurity.Since Centreon already monitors your assets (OS, web servers, databases, networking gear) and often knows their versions, we are considering an integration that crosses this data with real-time CVE (Common Vulnerabilities and Exposures) databases.The vision: A new security bulletin is released, and Centreon immediately flags the 15 servers in your infrastructure that are at risk—without you needing to trigger a manual scan.Before we dive deeper into this feature, we want to hear about your current reality:How do you manage vulnerabilities today? Do you use dedicated tools or is it a more manual process?

413

7 days ago

ltirandCentreonian

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.

52419

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

3879

5 months ago

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.

931

1 year ago

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

3965

1 year ago

Farzana-HUBONESteward **

Problem with Range Definition

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

10 days ago

blankSteward *

[ESX 8 API]get_esx_stats function failed to retrieve stats

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":[],"defaul

246

10 days ago

omercierCentreonian

NSClient++: bridging the gap

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

262

1 month ago

btrocmeSteward **

Plugin http : passer de expected-content en json+collection

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 v

626

1 month ago

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

14014

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

321

2 months 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

2027

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 ?

681

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]

602

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!

321

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

421

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 ?

1428

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

933

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.

1245

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.

441

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

121

SEBASTIEN97420Steward *

VMWare connector

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

695

perodoSteward *

supervision d'un FortiAp

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

1243

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

470

syrineSteward *