Centreon Infra Monitoring

Hi,I am looking for an advice on the best approach for the following.We currently have a linux server producing a custom metric for an internal application. This metric is currently simply logged in a file on the server.I was wondering if I could not use centreon for basic monitoring of this metric. T​​​​​o have alerting and easy historic access with a graph.I suppose there is different possibility for that. Maybe transform this metric into a custom snmp information that could be recovered by centreon for exemple. Or via the nrpe plugin. I was wondering what you would recommend to avoid as much customisation as possible and keep it as simple as possible.The real solution is to have observability of the app with something like open telemetry standard but this is too early for now. Regards,

 J’ai un problème j’ai migré de version actuellement sur la dernière en liste. sur mon centreon de test celui en prod étant en ancienne version. Cependant sur awx j’ai cette erreur pourtant rien n’a changé à part la version je n’arrive pas à comprendre si le soucis viens d’awx ou centreon.  \"/tmp/ansible_centreon_host_payload_hvia7iww/ansible_centreon_host_payload.zip/ansible/modules/centreon_host.py\", line 416, in main\n  File \"/var/lib/awx/venv/ansible/lib/python3.6/site-packages/centreonapi/webservice/configuration/host.py\", line 409, in getparams\n    return self.getparam(centreon_host_params)\n  File \"/var/lib/awx/venv/ansible/lib/python3.6/site-packages/centreonapi/webservice/configuration/host.py\", line 389, in getparam\n    current_param[p.split(\":\", 1)[0].strip()] = p.split(\":\", 1)[1].strip()\nAttributeError: 'dict' object has no attribute 'split'\n",    "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",    "rc": 1,}

Hello,I was able to follow the procedure step by step, as described in the online documentation, to migrate from version 24.04 to 25.10.The migration completed successfully; however, I am encountering an error when applying the configuration on the central collector :  [ - ] SRVA-CES1protocols: registering protocol ('file' (layers 1-3)protocols: registering protocol ('compression' (layers 6-6)protocols: registering protocol ('BBDO' (layers 7-7)endpoint applier: loading configurationReading main configuration file '/var/cache/centreon/config/engine/1/centengine.DEBUG'.The option 'auto_rescheduling_interval' is no longer available. This option is deprecated.The option 'auto_rescheduling_window' is no longer available. This option is deprecated.The option 'auto_reschedule_checks' is no longer available. This option is deprecated.Reading resource file '/var/cache/centreon/config/engine/1/resource.cfg'Warning Service 'Swap' on host 'ARCHIVESA-01' has a notification interval less than its ch

Bonjour à tous,Je vous souhaite une très bonne année pleine de succès et de réussite.je commence cette année avec une tentative d’upgrade de centreon de la version 24.04 vers 24.10 ou 25.10 mais j’ai exactement les mêmes messages d’erreur.  - nothing provides perl(Mojo::IOLoop::Signal) needed by centreon-gorgone-24.10.7-1.el9.noarch from centreon-stable-noarch-rh9  - nothing provides perl(Mojo::IOLoop::Signal) needed by centreon-gorgone-24.10.2-1.el9.noarch from centreon-stable-noarch-rh9  - nothing provides perl(Mojo::IOLoop::Signal) needed by centreon-gorgone-24.10.5-1.el9.noarch from centreon-stable-noarch-rh9  - nothing provides perl(Mojo::IOLoop::Signal) needed by centreon-gorgone-24.10.6-1.el9.noarch from centreon-stable-noarch-rh9  - nothing provides perl(Mojo::IOLoop::Signal) needed by centreon-gorgone-24.10.4-1.el9.noarch from centreon-stable-noarch-rh9  - nothing provides perl(Mojo::IOLoop::Signal) needed by centreon-gorgone-24.10.3-1.el9.noarch from centreon-stable-noarch-rh

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 for multiple hosts.This service can be transformed into a service template. A single service will be created for each linked host and will inherit the template you previously created.This update will be performed automatically during the Centreon platform update process (target: Centreon 25.10). Services by Host GroupCreating a service by host group allows for the same serv

We are facing an issue with the centreon_vmware process that started after a Centreon update applied in mid-December.Issue descriptionThe centreon_vmware service fails to start with the following error:# systemctl status centreon_vmware.servicecentreon_vmware.service - Centreon VMWareLoaded: loaded (/lib/systemd/system/centreon_vmware.service; enabled)Active: failed (Result: exit-code)Process: ExecStart=/usr/bin/perl /usr/bin/centreon_vmware.pl $OPTIONSStatus: 255/EXCEPTIONCan't use string ("Could not decode JSON from ''...") as a HASH refat /usr/share/perl5/centreon/script/credentialsencryption.pm line 55.LogsThe centreon_vmware.log shows the following messages:No vault config file given. Applying default: /var/lib/centreon/vault/vault.jsonNo Engine context config file given. Applying default: /etc/centreon-engine/engine-context.jsonThe given configuration file /var/lib/centreon/vault/vault.json does not exist.Something happened during init() method that makes Centreonvault not usable

Hello,Since the upgrade from 24.10 to 25.10, all ping services no longer work.I am using the “Base-Ping-LAN” template and the “base-centreon-ping” command.Linux ALMALINUX 9Over SSH, all my pings work correctly. In my firewall, ICMP traffic passes correctly.Version 25.10.4Was there any change between 24.10 and 25.10?How can this be resolved?I also set up a new VM and a clean installation of Centreon 25.10, I added a host for ping and I'm having the same issue.---------------------Français---------------BonjourDepuis le passage de 24.10 à 25.10, tous les services ping ne fonctionnent plusJ’utilise le modèle “Base-Ping-LAN” et la commande “base-centreon-ping”Linux ALMALINUX 9 En SSH, tous mes pings fonctionnent correctement. Dans mon firewall les flux ICMP passent correctement.Version 25.10.4Y a t’il eu un changement entre 24.10 et 25.10 ?Comment solutionner?J’ai aussi installé une nouvelle VM et une installation propre de centreon 25.10, j’ai mis un hote en ping et j’ai aussi le même sou

Hello everyone,I’m encountering an issue with the display of CMA data on the “Resource Status” tab. Context 1 — When Centreon was installed, two ACLs were created: “User” and “Admin” (I really mean the ACL, not the “Admin” option you can check on the user profile under the “Authentication” tab). The “User” ACL has limited access, but the “Admin” ACL has all permissions enabled across all ACL tabs. And of course, my admins are in the correct group associated with this ACL. Context 2 — We deployed several CMAs on servers, and they are fully visible in Centreon — everything works fine. My question is the following: Why can users with the “Admin” ACL (with everything checked) not see the CMA resources on the “Resource Status” tab, while a user with the “Admin” option enabled on their profile can see them? How can I allow the “Admin” ACL to access CMA resources? I think I’m missing something, which is why I’m asking for your help now. :) We have a Centreon 24.10 on a Debian 12 up to date. T

Hello,When i update Centreon from 24.10 to 25.10.I had some errors at update :    Exécution du scriptlet: centreon-web-25.10.2-1.el9.noarch                                                                                                                                                                            21/62Managing users and groups for apache ...Updating APP_SECRET in centreon environment files ...Updating centreon perl configuration files to central mode ...Managing apache and php fpm configuration and services ...Rebuilding Centreon application cache ...PHP Fatal error:  Declaration of Centreon\Application\Normalizer\IconUrlNormalizer::normalize($icon, $format = null, array $context = []) must be compatible with Symfony\Component\Serializer\Normalizer\NormalizerInterface::normalize(mixed $data, ?string $format = null, array $context = []): ArrayObject|array|string|int|float|bool|null in /usr/share/centreon/src/Centreon/Application/Normalizer/IconUrlNormalizer.php on line 40 

Hello,I’m running Centreon 25.10.3 on AlmaLinux, and I cannot create hosts from the web UI.When I try to create a host, I get:Error during creation (json encoding). See logs for more detail  The Centreon logs show:[2025-12-31T05:30:11+00:00] ERROR : Error during host/hostTemplate creation | {"custom":{"hostId":null,"isTemplate":false,"exception":{"message":"Syntax error","trace":"#0 ... json_decode() ..."}}}  I checked PHP-FPM and Apache logs there are no PHP errors or warnings. Memory and execution time are sufficient (memory_limit=128M, max_execution_time=0).I then tested the internal API:curl -k https://localhost/centreon/api/latest/platform/status Output:{"code":404,"message":"No route found for \"GET https:\/\/localhost\/centreon\/api\/latest\/platform\/status\""}  I also tried to run the supposed API install command:sudo -u apache /usr/share/centreon/bin/console centreon:api:install But got:There are no commands defined in the "centreon:api" namespace.  It seems the /api/latest r

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

Hello, I’m getting this error right after logging in with my Google account. If I refresh the page the error disappears, but it comes back every time I log in again. I’ve already cleared my browser cache, but it didn’t help. Has anyone had this issue before? Thanks in advance!

🇬🇧Hello,I’d like to monitor a few database files to track their growth and guide the developers. I started testing the CIFS plugin, but I can’t get accurate graphs for all the files in a folder. I finally found a syntax that works.​/usr/lib/centreon/plugins//centreon_protocol_cifs.pl --plugin=apps::protocols::cifs::plugin --mode=files-size --hostname='192.168.0.1' --cifs-username='DOMAIN/USER' --cifs-password='xxxxxxxxxxx' --timeout='' --file='/Depot/truc.1' --directory='/Depot' --max-depth='5' --warning-size='' --critical-size='' --verbose --file='/Depot/bidule.exe' --file='/Depot/machin.exe' --file='/Depot/Test.htm' --file='/Depot/chose.ps1'Listing all the files works, but obviously it doesn’t work if new files are added…So I have two questions:How can I monitor an entire folder without having to list every single file? Is that possible? How many files can I monitor without overloading the system? If I have 2,000 files, will Centreon go crazy trying to display all of them?When I

Hi,Since yesterday, Centreon has database issue + Collector down.I found that centreon-engine service is in activating state.in centreon-engine.log : [processing] [error] [688633] failover: global error: failover: 'central-module-master-output' cannot connect endpoint.[2025-12-04T12:17:22.520+01:00] [tcp] [error] [688633] TCP: Connection refused to localhost:5669[2025-12-04T12:17:22.520+01:00] [processing] [error] [688633] failover: global error: failover: 'central-module-master-output' cannot connect endpoint.[2025-12-04T12:17:37.521+01:00] [tcp] [error] [688633] TCP: Connection refused to localhost:5669[2025-12-04T12:17:37.522+01:00] [processing] [error] [688633] failover: global error: failover: 'central-module-master-output' cannot connect endpoint. Service status[root@SN-SUPERVISION-P centreon-engine]# service centreon-engine statusRedirecting to /bin/systemctl status centreon-engine.service● centreon-engine.service - Centreon Engine Monitoring Daemon     Loaded: loaded (/etc/syst

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 --hostname='vcenter.mycompany.fr' --port='443' --proto='https' --esx-name='esx1.myc

Bonjour, J’ai un soucis sur les services attachés à un groupe d’hotes. Les paramètres surchargés des macros ne sont plus pris en charge : par exemple : j’utilise le template Os-Linux-Disk-Generic-Name-SNMPje surcharge le champ DISKNAME avec / Cependant voici la commande générée  : sudo -u centreon-engine /usr/lib/centreon/plugins//centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=storage --hostname=monserveur --snmp-version='2c' --snmp-community='macommu'  --storage '' --name --display-transform-src='' --display-transform-dst='' --warning-usage='80' --critical-usage='90' --filter-perfdata='storage.space|used|free'Le problème n’est pas vrai lorsque je créé ce service directement rattaché à un hote J’ai lu apparemment centreon voulait abandonner le service par groupe d’hote ce que je trouve très dommage, est ce la raison pour laquelle ces métriques ne remontent plus ?Je vous remercie par avance pour vos réponses 

Hello,I’m still trying to understand what happens, but I just upgrade from 24.10.14 to 24.10.15 and this is a disaster.All gorgone to Remote Server flux are downAll flux for Centreon Broken are down.  I’m still investigating , but i urge you to no upgrade your production setup and test it before on a stagging.

Since i upgrade many plateform to 25.10 , i have 2 Host Groups menu  

We are using a SSO solution to centralize our user authentication flows and because of that users have many many groups.When trying to login through Centreon, those groups data are added within the authentication token, making it reach huge sizes (around 4k characters for now), but the structure of the database on the table “security_authentication_tokens” for the “token” field is limited to 255 characters. i got explained that it is possible within an openid request to ask for a filter on the groups to maybe reduce that token size.Is there something to do in that sense and how can we do it ? This is blocking the deployment of this auth solution at scale. 

Hi folks,Here my feedback/issue after go to 25.10Forced check doesn’t work anymore, success message after push it, but nothing happens When I create a new service, host, or modify anything, I have to restart all centreon stack : systemctl restart centengine to show up the new elements. Export config, restart engine from web is no longer enough Custom macros don’t work on service apply to hostgroup. (ok with linked on multiple hosts or host only)I migrate to a new platform (22.10 to 25.10) by following documentation ‘Migrate from an EL-type OS to another EL-type OS’ 

Bonjour à toutes et tous,J’ai installé dernièrement un serveur avec Centreon pour superviser des serveur Windows (Windows Serveur 2019 DataCenter build 1809)La supervision avec le CMA en mode sans SSL fonctionne parfaitement,J’ai voulu passer en SSL et la plus de communication entre mes hôtes et le collecteur.J’ai fait le test avec un certificat autosigné et avec un certificat provenant de notre autorité de certification interne.J’ai sans doute loupé une étape. Merci de votre aide.

 I have installed the it-100 license, when I try to update a plugin or install a new one I get this error 

Hi everyone,I’m looking for the most efficient way to generate a list of active services (excluding templates) that do not have any contactgroup defined—neither directly nor inherited from templates.I’d like to explore different methods to achieve this, such as:SQL queries (directly querying the Centreon database) REST API (if applicable) Parsing configuration files (e.g., .conf files in /var/lib/centreon-engine/central/config/)If you’ve already tackled this issue or have any insights, I’d appreciate your input! Which method do you recommend for accuracy and simplicity?Thanks in advance for your help!

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 ? 

Hello Centreon Community/Support,I am experiencing an issue with a custom Lua stream connector script that is designed to send monitoring events to an external system (BEM). The script functions correctly on one Centreon Poller/Central server, but on a different host (which I'll refer to as "Problem Host"), events are consistently being dropped at the filter stage, resulting in the debug log message filter' returned false.I have confirmed that the target system is listening on the expected port (2540) and that the "Problem Host" can establish a TCP connection to it.Problem Description:On a specific Centreon host (the "Problem Host"), the Centreon Broker Lua stream connector is not processing events as expected. The debug logs show that the filter function in the Lua script is rejecting all incoming service status and host status events, even though the same script works perfectly on another Centreon host. This prevents any alarm messages from being sent to the BEM system.Observed Debug