Centreon Infra Monitoring

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?

604

4 days ago

lpinsivyCentreonian

Removing the ability to create services linked to multiple hosts or host groupsFeature Sunset

Dear users, In order to simplify and improve the user experience of our software, we plan to remove two features in an upcoming major update:Creating services linked to multiple hosts. Creating services by host group.We understand that these features may still be used by some of you, but we believe they can be replaced by the use of templates. We are making this decision to optimize the software and make it more intuitive. Proposal of solutions when updating the Centreon platform Services linked to multiple hostsCreating a service linked to multiple hosts allows you to have an identical configuration of this service f

42016

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

53319

3 months ago

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

3889

5 months ago

fmattesCentreonian

BBDO2 Deprecation with Centreon 25.10 ReleaseFeature Sunset

We wish to inform all users that BBDO2 will be officially deprecated with the 25.10 release of Centreon. This change is part of our ongoing effort to enhance the platform’s performance, security, and compatibility with modern infrastructure requirements. What is BBDO? BBDO, for Binary Broker for Data Operations, is a core protocol for exchanging monitoring data between a Centreon central server and pollers/remote servers. Why is BBDO2 Being Deprecated? With Broker 22.04.0, we have introduced a new version of BBDO based on Google Protobuf 3.The new protocol remains compatible with the previous one, but introduces new events.There are several key reasons for the depreciation of BBDO2:Performance improvements Flexibilit

1820

11 months ago

rchauvelCentreonian

Reminder of Centreon Version 23.04 End of Life (EOL)News

Reminder: Centreon Version 23.04 End of Life (EOL) Approaching SoonAs per the Centreon product lifecycle, we would like to remind all Centreon users that Centreon version 23.04 will soon reach its end of life (EOL). It is crucial to ensure that your infrastructure remains secure and up-to-date by upgrading to a supported version.If your platform is currently on version 23.04, it is highly recommended to upgrade to a newer version to continue receiving security updates and support. The upgrade process is thoroughly documented and can be accessed here.Thank you for your prompt attention to this important matter and for your continued support in keeping your systems secure. Stay ahead of potential threats by subscribin

2580

rchauvelCentreonian

End of Support for Debian 11 in Version 24.10Centreon 24.10

📢 End of Support for Debian 11 in Version 24.10 🚨We want to inform our user community that with the upcoming release of Centreon 24.10, support for Debian 11 will officially come to an end.Debian 11 is already in Long Term Support, and Centreon has been supporting Debian 12 since 24.04.We will support in-place OS upgrades from Debian 11 to Debian 12 which you can perform with 24.04 before upgrading to Centreon 24.10.We appreciate your understanding as we continue to focus on providing the best possible monitoring solutions.For any questions or support, please don’t hesitate to reach out via our community forums or customer support. We’re here to help! Don't forget to subscribe to the Latest News, Product Updates

60910

published in Infra Monitoring Data usage and Visualization

rchauvelCentreonian

Legacy MAP Retirement [Updated 09/30/24]

[Update 09/30/24] This update confirms that MAP Legacy will be retired with 24.10 This is an announcement that Centreon will retire Centreon MAP Legacy starting next version 24.10. The diagramming and mapping functionality referred to as Centreon MAP is currently shipped in two flavors:MAP Legacy which relies on a client application running on a desktop to create/edit maps MAP Web, a web client fully embedded into the Centreon user interfaceThe following only relates to Ce

3831

published in Infra Monitoring Data usage and Visualization

smauCentreonian

Cloud Release (June 2024) - What's new in Dashboards?New dashboards

Hello Dashboards users! We are pleased to announce the release of Centreon Cloud, June 2024!New features and enhancements are now available for Cloud users, let's take a look at what's new...General AvailabilityNo more Beta mention. Centreon Dashboards are now generally available for Cloud users.Two new widgetsStatus ChartThis widget displays the distribution of current statuses on selected resources, as a chart.Business Activity DiagramThis widget displays graphically a business activity hierarchy of KPIs and lets you navigate thr

750

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.

951

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

published in Infra Monitoring Data usage and Visualization

rchauvelCentreonian

[UPDATED] Deprecated views will be retired [in an upcoming] major versionProduct updates

[UPDATE AS OF 02/12/2024]As we are progressing towards next major release and still receiving feedback for required features in Resource Status we have decided to take a step back and NOT retire deprecated views in the Spring 24 version.We are planning the Fall version and will prioritize those enhancements in order to be in a position to then retire those views.Stay tuned and continue sending your valuable feedback![END OF UPDATE] It had been announced a long time ago that the plan was to remove the legacy host and services views as those are now replaced with Resource Status. This was visible both in the documentation as well as in the product.

66117

2 years ago

PhilippeSteward **

CMA - Personnalisation des sondes embarquées (Windows Update / Pending Reboot) et de leur planification

Bonjour,Je souhaite avoir des précisions concernant les services de supervision embarqués dans Centreon Monitoring Agent (CMA), notamment sur leur personnalisation.Environnement OS : Red Hat Enterprise Linux 9.6 Plateforme : Centreon 25.10.9 Architecture : Centreon + Poller + DB sur le même serveur SELinux désactivé ContexteLors du déploiement de CMA sur les serveurs, nous constatons que les sondes embarquées sont bien présentes, mais nous ne trouvons pas de moyen clair pour personnaliser leur configuration.En particulier : l’entrée de registreComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Centreon\CentreonMonitoringAgent ne semble pas indiquer de fichier de configuration permettant de m

6 hours ago

PhilippeSteward **

Discovery rule inclusion filter not working with regexp on interface names

Hello,I’m facing an issue with a discovery rule in Centreon where the inclusion filter does not seem to work as expected.Context: I created a discovery rule to include only interfaces with names containing StackPort. My inclusion rule is configured as: Macro: $name$ Regexp: ^StackPort* Expected behavior:Only interfaces like StackPort1, StackPort2, etc. should be discovered.Actual behavior:When I run the discovery command manually, I can see interfaces such as:'StackPort2' [speed = 160000][status = up][id = 124][type = propVirtual]Howeve

101

22 hours ago

PhilippeSteward **

Newly discovered services not visible to users until ACL reload

Hello,I’m encountering an issue with ACL behavior after service discovery in Centreon.Environment: OS: Red Hat Enterprise Linux 9.6 Centreon version: 25.10.9 (Central + Poller + MySQL 8) SELinux: disabled Context: I have configured user ACLs to restrict actions (menus, features, etc.). For resources, I did not create any specific restriction since all users should see all resources. Therefore, I am using the default “All Resources” ACL. Issue:When new services are discovered via service discovery: Non-admin users cannot see the newly created services. Even after logging out and

22 hours ago

RicoSteward **

asked in Infra Monitoring Data usage and Visualization

graph legend is now "default"

Hello,Since my last upgrade to 24.10.12, some of my graph’s legends are broken.the metrics are correctly named, but the graphs legend shows “default” instead of metric name.for example : performance data and the graph is : graph legendin parameters > data, metrics name are OK for this service. Any idea how to fix this ?

Alexandre BelhommeBuilder **

Centreon log management - Support for On Premise infrastructure

Hello, just wondering because i’m unsure about what i read and heard about the new Log Management product.Is this only something that is available in Cloud or is product able to be installed within existing on premise installations of centreon Infrastructure Monitoring ?I heared that Centreon has some “special sauce” to improve reliability and scalability to ensure log ingestion but i didn’t read explicitely if there was support for on premise installation and i would like some precisions on that.Thank you

ahartungBuilder *

Centreon RedHat 9 + Centreron 24.10 - new install

Hi, i installed a new VM - REDHAT 9 .. STEP 2 https://docs.centreon.com/docs/24.10/installation/installation-of-a-central-server/using-packages/#step-2-installation dnf install -y centreon-mariadb centreon whats wrong ? Error: Transaction test error: file /usr/share/mysql/charsets/Index.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64 file /usr/share/mysql/charsets/armscii8.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64

41613

Stéphane

Sudoers alias duplicate

Hi,[root@centreonpollerorcentral sudoers.d]# grep User_Alias /etc/sudoers.d/*[Cc]entreon*/etc/sudoers.d/centreon:User_Alias CENTREON=%centreon/etc/sudoers.d/centreon-gorgone:User_Alias GORGONE=centreon-gorgone/etc/sudoers.d/centreon-plugins:User_Alias CENTREON_COLLECT_USERS=centreon-engine,centreon-gorgone/etc/sudoers.d/sudoersCentreonLinuxPlugins:User_Alias CENTREON_COLLECT_USERS=centreon-engine,centreon-gorgoneIt raises a warning from sudo, also, what’s this sudoers entry for?

101

gherisseSteward *

[LDAP] LDAP(s) configuration mirrors previous centreon infrastructure but doesn't retrieve any user

Hello, I’m currently migrating our centreon on-premise infrastructure to a new set of servers, and I’m trying to import my AD users again on the new platform. However I mirrored the configuration of the previous platform, but in trying to import users, nothing is found. The alias is resolved, the 636 port is not blocked, and certificate is integrated to the trust bundle. Do you know where I could find the logs of this part of the LDAP connector ? I know where to find the system’s LDAP attempts but not this one… Thanks ! Cheers

521

midwintergatesSteward *

Services status unknown after update?

Hi,I recently updated to version 24.10.15 from 24.10.14I also updated some third party plugins at the same time.Since that update I have had the problem that occassionally the services running the plugins (Dell iDRAC among others) are timed out after a while. Could be every other hour or after a day or two.All services using those plugins are moved to “Unknown” with information “(Process Timeout)”Restarting the poller in the GUI solves the problem but why is this happening and any solution?Running the same plugin in the CLI works without any problems so it seems to be a poller issue. OK: All 2 components are ok [2/2 psus]. | 'PSU1#hardware.powersupply.power.watt'=200W;;;0; 'PSU2#hardware.powersupply.power.watt'=180W;;;0; 'hardware.psu.count'=2;;;;Checking poer suppliespower supply 'PSU1' status is 'ok' [instance: 1.1] [value: 200]power supply 'PSU2' status is 'ok' [instance: 1.2] [value: 180]

23215

Tony ZhangSteward *

Failed to execute check_drivesize: 2: ϵͳÕÒ²»µœÖž¶šµÄÎÄŒþ¡£

I am usring /usr/lib64/nagios/plugins/check_centreon_nrpe3 to monitor windows CPU/Memory. And centreon can get CPU & Memeory status. But when I use the same command try to monitor disk space, system show error:Failed to execute check_drivesize: 2: ϵͳÕÒ²»µœÖž¶šµÄÎÄŒþ¡£. The full command is bellow./usr/lib64/nagios/plugins/check_centreon_nrpe3 -H 10.3.3.200 -p 5666 -2 -P 8192 -2 -P 8192 -n -c check_drivesize -a "drive=C:" Centreon version is 25.10. NSClient version is 0.11.24 The nsclient.ini files: [/modules]CheckEventLog = 1CheckNSCP = 1CheckSystem = 1CheckDisk = 1CheckService = 1WEBServer = 1NRPEServer = 1NSClientServer = 1CheckExternalScripts = 1CheckHelpers = 1[/settings/NRPE/server]verify mode = peer-certtls version = tlsv1.2+insecure = falsepassword = *allowed hosts = 10.3.3.10,127.0.0.1port=5666

Christophe MontabrutSteward *

Redémarrage du collecteur tous les jours

Bonjour,Depuis que j’ai migré vers la version 25.10.5, je suis obligé de redémarrer mon collecteur tous les jours.Le matin je me connecte et le collecteur semble tourner mais nb de machines : 0 et sur la ligne je retrouve la date de la dernière mise à jour de mon collecteur sur fond Orange.Je redémarre mon collecteur et tout se remet à jour naturellement...Comment puis-je outrepasser cette opération qui n’était pas nécessaire sur la version précédente. Il doit y avoir un paramètre qui bloque l’uptime du collecteur.Merci pour vos retoursBonne journée

192

3 days ago

HenryHSteward *