Recently active topics

Available connectors

During the beta, three connectors are available in Rust. For GA, the next goal is to gradually convert the existing SNMP connectors, with no breaking changes for users. Rust connector Perl equivalent in the catalog Status Documentation Generic SNMP (Rust) Generic SNMP Experimental Connector page Linux SNMP (Rust) Linux SNMP Experimental Connector page Windows SNMP (Rust) Windows SNMP Experimental Connector page

300

fgbetokpanouCentreonian

Installation guideGuide

Understanding and writing a collection (Rust Collections guide)What you need on the poller Writing a collection Running the command and options Troubleshooting and logsInstalling and using a connectorGeneric SNMP (Rust) Linux SNMP (Rust) Windows SNMP (Rust)Rolling backRust templates have the -Rs-custom suffix and do not modify your Perl templates. To roll back, disable the hosts and services that use them, then deploy the configuration. You can then uninstall the centreon-plugin-*-snmp-rs and centreon-plugin-rust-snmp packages from your pollers.

310

fgbetokpanouCentreonian

Changelog

One line per release, most recent at the top. The "Impact on your collections" column flags breaking changes, as set out in the charter. Date Plugin version Format version Type Change Impact on your collections 09/30/2026 20260900 0 New feature Beta opening: centreon-plugin-rust-snmp executable; Generic SNMP (Rust), Linux SNMP (Rust) and Windows SNMP (Rust) connectors None Possible types: New feature, Fix, Breaking change.For a breaking change, the last column states what the tester needs to change in their collections.

240

fgbetokpanouCentreonian

Beta program charter

The beta covers only centreon-plugin-rust-snmp and its SNMP collections. It lasts about 6 months from September 30, 2026. It is not intended for business-critical production. DisclaimerThe versions distributed during this program are beta versions. We do not recommend using them to monitor business-critical production devices. The JSON file format (see the format attribute) may still change in ways that break existing collections. If that happens, it will be announced in the changelog.ScopeItem Covered by the beta Plugin centreon-plugin-rust-snmp Collections Generic SNMP (Rust), Linux SNMP (Rust) and Windows SNMP (Rust) connectors, all experimental Protocol SNMP v2c only. SNMP v3 is out of scope (planned for GA; check the changelog in case it becomes available during the beta) Distributions RHEL and derivatives 8, 9 and 10 (x86_64); Debian 12 and 13 DurationOpening: September 30, 2026. Duration: about 6 months. Beta exit (GA): from March 2027, depending on observed matu

280

fgbetokpanouCentreonian

Welcome to the Rust SNMP collection beta programBeta Rust

Thank you for joining the program.Why move from Perl to Rust? SNMP collection mode already existed in Perl. It let you run SNMP checks from a JSON file instead of a code module. This mode was easier to handle for users, but slightly less efficient than a dedicated plugin. We have rewritten it in Rust as a compiled binary with no Perl dependencies. This executable will be used to improve the performance of other existing SNMP connectors, and can later serve as the foundation for other collection families (HTTP in particular).What we expect from youInstall the Rust SNMP collection on a test or non-critical environment, alongside your Perl plugins, to compare its performance and results (statuses, values, metrics) with those of the Perl plugin on your own devices. Report bugs, discrepancies in results, and any unclear parts of the documentation. Give us feedback on the JSON format: in particular, is it easy to write and read? If you wish, share the JSON collections you write for your dev

350

fgbetokpanouCentreonian

Program description and how it worksGuide

The beta program opens on September 30, 2026 and will run for about 6 months.Its main goal is to test the new Rust SNMP collection in real-world conditions (performance as well as ease of use), ahead of a GA targeted from March 2027.Short descriptionCentreon is opening a beta program for its new Rust-based collection for SNMP checks. The principle remains that of collection mode: a connector is described in a JSON file (SNMP queries, macros, thresholds), with no code to write. The engine, however, is now a compiled Rust binary. We are looking for users willing to test it on their own devices and share their feedback before GA.Fact sheet: how the Rust SNMP collection worksWhat changes for youSimplified development: a new SNMP connector is described in a JSON file instead of a Perl module. Easier community contributions: a documented JSON file is easier to submit than a Perl module. Improved performance: the engine is a compiled Rust binary. The gains measured internally are significant

370

asked in Community Requests & Feedback

benjamin.biguetSteward *

[CENTREON-HA][24.10] My two database nodes are slaves.

Hello,My two database nodes are now slaves after an unsuccessful attempt to switch from slave to master.I am looking for a way to switch my primary node back to MASTER status. Currently, it is the active one operating in the HA setup. Previous command # pcs resource move ms_mysql Error: to move promotable clone resources you must use the promotable clone id (ms_mysql-clone) Error: Errors have occurred, therefore pcs is unable to continue # pcs resource move ms_mysql-clone Warning: Creating location constraint 'cli-ban-ms_mysql-clone-on-BDD_SECONDARY_NODE' with a score of -INFINITY for resource ms_mysql-clone on BDD_SECONDARY_NODE. This will prevent ms_mysql-clone from running on BDD_SECONDARY_NODE until the constraint is removed This will be the case even if BDD_SECONDARY_NODE is the last node in the cluster Result:[root@BDD_SECONDARY_NODE]# /usr/share/centreon-ha/bin/mysql-check-status.shConnection SLAVE Status 'BDD_PRIMARY_NODE' [OK]Connection SLAVE Sta

120

9 days ago

Roterdan_macedoSteward **

Open Tickets Acknowledge respect centreon host acknowledge services configDiscussion ongoing

Hi, when I open a host's ticket via open-tickets using dashboard or via notification connector centreon_notification_centreon_opentickets_api.pl , only the host receives the ACK, even though the default acknowledgement configuration is set to “acknowledge services attached to the host”.My idea is to make the open-tickets ACK to respect the default acknowledgement configuration for hosts, or this parameter should be configurable within the provider rule.

245

Amélioration de Centreon Map : Support des images >2MB et SVGReleased

total-soc-csoc.ocdSteward *

Bonjour à tous,Je souhaite proposer une amélioration pour Centreon Map qui, je pense, pourrait bénéficier à de nombreux utilisateurs.Contexte : Actuellement, Centreon Map limite la taille des images à 2MB et ne supporte pas les fichiers SVG. Cette restriction pose des défis lorsque nous voulons intégrer des images de haute qualité ou des graphiques vectoriels, qui sont souvent essentiels pour une visualisation claire et précise de notre infrastructure.Proposition d'amélioration :Augmenter la taille maximale des images supportées au-delà de 2MB : Avec l'augmentation des résolutions d'écran et la nécessité d'images détaillées, il serait bénéfique de permettre l'importation d'images de plus grande taille. Cela éviterait la perte de qualité due à la compression excessive. Supporter les fichiers SVG : Les SVG (Scalable Vector Graphics) sont des graphiques vectoriels qui offrent une qualité d'image supérieure à n'importe quelle résolution, sans perte de qualité. En permettant l'utilisation d

1169

PaloAlto FW - new mode to check SSL certificatesIn Backlog

joschi99Steward **

Paloalto firewalls use internal ssl certificates. It should be important to monitor this certificates through SSH:admin@fw01-bz> show sslmgr-store config-certificate-infoAF05329B:A856B404C25A48A0C02F0A7A3A2036925B9BA5C2 serial number: issuer: /CN=81.161.232.189 issuer-subjecthash: A856B404C25A48A0C02F0A7A3A2036925B9BA5C2 issuer-keyhash: db-type: V db-exp-date: 321008075404Z(Oct 8 07:54:04 2032 GMT) db-rev-date: () db-serialno: AF05329B db-file: unknown db-name: /CN=vpn.i-vertix.com db-status: V7CE5E3F56B1AB38C4D0BC440823B9E9:273F5E283B4F4D0879716CD0E32A886B8195C0F3 serial number: issuer: /CN=Microsoft Azure Federated SSO Certificate issuer-subjecthash: 273F5E283B4F4D0879716CD0E32A886B8195C0F3 issuer-keyhash: db-type: V db-exp-date: 251011072048Z(Oct 11 07:20:48 2025 GMT) db-rev-date: () db-serialno: 7CE5E3F56B1AB38C4D0BC440823B9E99unknown db-file: unkn

18016

HTML/formatted NotificationIn Backlog

omercierCentreonian

Persona: All users receiving notifications Problem to solve: Default notifications are poorly formatted, no colorization, no highlight... Expected outcome: Immediate readability of what resource is impacted what is the status Less alert fatigue Potential solutions: https://github.com/Shini31/centreon-notifications or this fork https://github.com/masgo/centreon-notifications Support of markdown-formatted messages Based on Github proposition.

1494

Create an autologin url leading to Resource Status pagesDeclined

GMicasSteward *

Hi, I would like to be able to create auto-login URLs that lead directly to the resource status pages rather than to the deprecated status detail pages.The goal would be to provide direct access to the popup displayed when selecting a service from the Resource Status page.At present, only the deprecated status detail pages can be accessed through automatically generated URLs. Regards,Gaël

472

cloud::prometheus::exporters::cadvisor::plugin > Add Filter on NamespaceNeeds Votes

romsworldSteward **

Hi,Could you add a filter for namespace for plugin cloud::prometheus::exporters::cadvisor::plugin ?The name of namespace is on the output when we list-containers, so it will be easy to add the filter :) /usr/lib/centreon/plugins//centreon_prometheus_cadvisor_api.pl --plugin=cloud::prometheus::exporters::cadvisor::plugin --mode=cpu --hostname=*** --url-path='/api/v1' --port='80' --proto='http' --credentials --username=*** --password=*** --container='container=~"moncontainer"' --pod='pod=~".*"' --verbose --mode=list-containers [container_name = moncontainer][pod_name = monpod-55d94dc4cc-rtmxg][namespace = MONNAMESPACE]Thanks a lot

111

Création d'un check du DTU sur les éléments AzureNeeds Votes

schockeelSteward *

Bonjour,Nous sommes dans une infrastructure hybride Cloud Azure / OnPrem. De ce fait nous avons pas mal de base de données Cloud Azure et nous utilisons donc le connecteur dédié.Le connecteur Azure SQL Database propose notamment de surveiller la consommation CPU et RAM des BDD mais pour nos utilisateurs des équipes projet applicatif ces métriques ne sont pas pertinentes Pour eux il est beaucoup plus pertinent de surveiller la consommation DTU des bases de données Azure.Donc lorsqu’il y a une mise en production d’une application et qu’elle comprend une BDD Azure, les équipes nous demandent systématiquement de monitorer la consommation DTU.Actuellement nos monitorons cette consommation DTU mais via des check custom avec script ps1 avec une exécution distante en NRPE. C’est donc pour cette raison que je me permet de vous faire cette proposition de création de commande de check DTU. Cette métriques étant systématiquement demandée, je pense qu’il serait intéressant et pertinent de le rajou

401

Display parent/child host relationships in the Resources Status pageNeeds Votes

TomlbSteward *

Hi, We have configured parent-child relationships between hosts, and we would like this parentage information to be visible somewhere in the Resources Status page.This could be implemented, for example, as:An additional column showing the parent/child relationship for each host, and/or Additional information displayed in the side panel when selecting a host/serviceThis would make it easier to quickly identify dependency relationships between hosts directly from the Resources Status view, without having to navigate to another page. Regards,Thomas

412

Color mismatch for Unreachable hosts between the top banner and Resource Status pagePlanned

TomlbSteward *

Hi, We have noticed a visual inconsistency in the monitoring interface regarding the color used to represent hosts in an Unreachable state (child hosts whose parent host is Down). In the top banner (Hosts counter), unreachable hosts are counted and displayed in orange. In Resource Status, the same hosts display an Unreachable status badge in grey. This is confusing for operators.Aligning the color of the Unreachable status across the top banner and the Resource Status page would make things much easier for our operators. Would it be possible to implement this? Regards,Thomas

372

Get macros in service listing API endpointNeeds Votes

mikailSteward **

Hello,Currently, we can retrieve the macros from the services by targeting the service itself in the endpoint : /api/latest/configuration/services/{service.id}.The macros are absent when checking for several services : /api/latest/configuration/servicesWould it be possible to add an option to fetch the macros in that endpoint ? Currently, if we want to retrieve the macros from the configuration, we have to make a request for each service.

111

Add the feature "poller locked"Discussion ongoing

DalfoCentreonian

Sometimes the team that administrate Centreon is different from the ones that make the daily configuration, like adding new host.This could lead to some scenario where you have overused pollers and underused pollers.Maybe we can add a feature that could “lock a poller”:The default poller can not be locked and viceversa. You can’t see nor select a locked poller if you add a new host If you duplicate an host monitored by a locked poller, it will lbe monitored by the default. Thanks for reading!

312

sdouceBuilder **

VEEAM13Planned

Veeam has released version 13, which is no longer compatible with the current Centreon connectors.In this version, access is only available through the REST API:https://helpcenter.veeam.com/references/vbr/13/rest/1.3-rev0/tag/LoginVeeam is now provided as a Linux appliance with specific command sets.Could you please consider updating the Centreon plugin to support this new version and its REST API access?

47617