Skip to main content

Recently active topics

111
lpinsivy
Centreonian
lpinsivyCentreonian
 Infra Monitoring Platform
Major Evolutions for Centreon Infra Monitoring 26.10 LTS: Heading Towards Next-Generation OSCIentreon 26.10

The upcoming major release of Centreon Infra Monitoring (CIM) 26.10 LTS will mark a key milestone in the modernization of our software architecture. To ensure optimal performance, enhanced security, and long-term stability, this new version will extend its compatibility to next-generation operating systems. Users will be able to deploy CIM 26.10 on Enterprise Linux distributions (RHEL, AlmaLinux, Oracle Linux) versions 9 and 10, as well as the upcoming Debian 13 major release. However, this technological transition requires strategic choices to maintain our quality standards. Consequently, official support for Debian 12 and Enterprise Linux 8 (EL8) will be discontinued with this release. These older operating systems no longer align with the 3-year lifecycle inherent to our Long Term Support (LTS) versions. We invite our users to start planning their infrastructure upgrades to the targeted platforms now, ensuring a smooth transition and full enjoyment of the innovations in CIM 26.10 LT

1525
lpinsivy
Centreonian
J
joveniaux jeremySteward *
 Infra Monitoring Platform
Centreon 25.10.13 - Broker fails after configuration export with "No usable encrypted password: bad decrypt"

Hello,I am experiencing an issue after upgrading my Centreon server to 25.10.13.EnvironmentCentreon Central: 25.10.13 Centreon Web: 25.10.13 Centreon Broker: 25.10.7 Centreon Engine: 25.10.7 MariaDB: 10.11.18 AlmaLinux 9ProblemAfter exporting the configuration from the Centreon Web interface, the broker configuration file is regenerated and the database password is written as an encrypted value:"db_password": "encrypt::..."When cbd starts, it immediately fails with:No usable encrypted password: Decryption finalization failed: error:1C800064:Provider routines::bad decryptThe broker continuously crashes and is restarted by the watchdog.Investigation performedMariaDB is running correctly. The centreon database account works correctly. Manual connection to centreon_storage succeeds:mysql -u centreon -p centreon_storage/etc/centreon-engine/engine-context.json exists. Gorgone, Engine and MariaDB are running correctly. Symfony secrets seem healthy:php /usr/share/centreon/bin/console secrets:l

613
fmattes
Centreonian
E
emeckSteward ***
sdouce
sdouceBuilder **
Support for Additional Exporters in Centreon Monitoring AgentNew

I would like to propose an enhancement to the Centreon Monitoring Agent (CMA) by introducing support for additional exporters ("extra exporters"), allowing the agent to send collected open telemetry to multiple destinations simultaneously. Introduce an optional extra_exporters section in the CMA configuration.Example:{ "endpoint": "centreon.example.com:4317", "encryption": "full", "token": "...", "host": "server01", "extra_exporters": [ { "type": "otlp", "endpoint": "alloy01:4317", "tls": false } ]}The existing Centreon exporter would remain unchanged and continue to be the primary destination.The additional exporters would receive the same telemetry in parallel.  We can have so this benefitsSingle agent deployment for multiple observability platforms. No duplicated data collection. Reduced CPU and memory footprint compared to running multiple agents. Better integration with the OpenTelemetry ecosystem. Easier adoption of hybrid monitoring architectures. No i

1
20
sdouce
P
PerBaccoSteward *
 Centreon IT-100 users
Authentication failed, company not found

Hi,in my Centreon on premise version 25.10.9, if i go the page:Configuration → Connectors → Monitoring Connectorsand i click to the botton “Update all”, i get this error: “An error occured while installing the following monitoring connector :+ base-genericReason: Authentication failed, company not foundSo the following monitoring connector were not processed+ base-generic” while on file /var/log/centreon/license-manager.log a this line appears [2026-04-07T15:35:24+02:00] ERROR : 0|0|[RestUnauthorizedException] https://api.imp.centreon.com/v2/auth/instance : Authentication failed, company not found | {"custom":null,"exception":null,"default":{"request_infos":{"uri":"/centreon/api/internal.php?object=centreon_pp_manager_pluginpack&action=updateAllPluginPacks","http_method":"GET","server":"10.40.11.150"}}} The license is an IT100This issue happened after the upgrade from version 24.* to 25.* How can i fix this issue?     

13411
S
E
emeckSteward ***
F
Feley Milton Brabeck AMOUZOUSteward *
lpinsivy
Centreonian
lpinsivyCentreonian
 Latest Security Bulletins
June 2026 monthly security bulletin for Centreon Infra Monitoring - HIGHSecurity Bulletin

Publication date: June 30th, 2026 Component: centreon-webList of vulnerabilities: 1 Description: Fixed multiple SQL injection vulnerabilities in legacy PHP code that could allow authenticated users to perform unauthorized database operations.Reference: N/ACVSS: 8.8Severity: HighStatus: Fixes have been provided for all supported versions and it is recommended to update Centreon Web on Central Server:Centreon Web 25.10.15 Centreon Web 24.10.28  Component: centreon-it-edition-extensionsList of vulnerabilities: 1 Description: Fixed an information disclosure issue in the IT Edition Dashboard Playlist feature where internal error details could be exposed in API responses.Reference: N/ACVSS: 3.4Severity: LowStatus: Fixes have been provided for all supported versions and it is recommended to update IT Edition Extensions on Central Server:Centreon Open Tickets 25.10.6 Centreon Open Tickets 24.10.13 Stay ahead of potential threats by subscribing to the Security Bulletin section. You’ll receive i

540
lpinsivy
Centreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
rchauvel
Centreonian
rchauvelCentreonian
H
Hameed RahmanSteward *
 Infra Monitoring Platform
Deadlocks and Locks-Waits services showing UNKNOWN after Centreon upgrade

We are experiencing an issue after upgrading Centreon to the latest version. We recently upgraded our Centreon platform to the latest version 24.10.27 and have observed an issue affecting multiple monitored serviceSince the upgrade, several services that were previously working correctly are now reporting an UNKNOWN status.The plugin output reported for the affected services is: - UNKNOWN: No locks counter found with given filters- UNKNOWN: No locks waits counter found with given filtersWe would like to understand if:- There are any known issues after upgrading Centreon that could cause services to return UNKNOWN status.- Any plugin changes or compatibility issues introduced in recent Centreon versions could explain this behavior.- There are any known fixes or troubleshooting recommendations for similar cases. Any guidance or suggestions would be greatly appreciated.

90
H
E
emeckSteward ***
Passing credentials through MySQL/MariaDB service templates to override host's credential macrosDiscussion ongoing

Hello. The MySQL/MariaDB connector stores the credentials in the monitored host's macros. The problem is that if I need to have a service that connects to the server of that monitored host but with another user, there is no way to override the "default" credentials from the host's macros. We have several MySQL servers with several databases and users in each that we need to monitor. So for now, you need to create a new monitored host (for the same server) with those credentials or use a modified command based on the one provided by the connector. Could it be possible to add that functionality (overriding the credential stored in the host) to the service templates for the MySQL/MariaDB connector? That also be consistent with how other connectors work, which allow to override macro's values stored in the host with its own macros or passed as options in the EXTRAOPTIONS macro (for example, hostname, protocol, port...). The connector allows to specify a database and port to connect to; it

1
163
E

Badge winners

  • First Question Answered
    Metfanhas earned the badge First Question Answered
  • Social Expert
    Philippehas earned the badge Social Expert
  • First Question Answered
    Philippehas earned the badge First Question Answered
  • Five Questions Answered
    SavCenthas earned the badge Five Questions Answered
  • First Topic Created
    Hameed Rahmanhas earned the badge First Topic Created
Show all badges
Terms & ConditionsAccessibility statement