Centreon Infra Monitoring

Bonjour a tous, Je viens tout juste de mettre à jour mon Centreon de la version 22.04 à 24.10, et l’opération s’est bien déroulée. Les versions du central et des pollers sont à jour, tout comme le serveur de base de données, qui utilise désormais MariaDB 10.11.Cependant, je rencontre un souci d’affichage global de l’interface web. Il semble que Centreon n’arrive pas à charger correctement le thème, même après avoir vidé le cache de mon navigateur.Test fait en ingconito, meme resulta.Auriez-vous une piste ou une solution à me proposer, s’il vous plaît ?A savoir que je suis sur AlmaLinux 8.Merci d’avance pour votre aide.;) 

Hello,I’m currently experiencing an issue in the Service Discovery module of Centreon.When trying to scan services for a specific host, the search field should suggest the host as I start typing its name (after entering the first 3 letters, for instance). However, in my case, no suggestions appear, even though the host is properly configured in the system and enabled.🔍 Expected behavior:When typing the first letters of a host name (e.g., "Cen"), the host "Centreon-Server" should appear in the suggestion list.🐞 Observed behavior:No suggestion is shown, even though the host exists and is fully configured (status: enabled, correct poller, and template applied).📎 Attached screenshots: Host Configuration (Host “aaaaaa” exists and is enabled)     Service Discovery search box (typing “Centreon” returns nothing)     Could you please advise if this is a known issue or if there are specific requirements for the host to appear in the Service Discovery module?Thanks in advance for your help.

Hello,I’m using the Debian Bookworm Centreon image you provide. The loading of the “Loading monitoring connectors” is very very slow, but more generally browsing in any page is quite slow I tuned few Mariadb SQL Backend settings and also tuned some PHP settings but it’s still very slow What is strange is that the CPU usage and memory usage is not full (around 50%) Any idea would be very appreciated Many thanks 

Bonjour,Je souhaite installer Centreon 24.10 sur AlmaLinux 8.10. Selon la documentation officielle de Centreon  les paquets de la version 24.10 sont compatibles avec AlmaLinux 8, AlmaLinux 9, RHEL 8/9, Oracle Linux 8/9 et Debian 12.Voici les informations de mon système :NAME="AlmaLinux"VERSION="8.10 (Cerulean Leopard)"PLATFORM_ID="platform:el8"Donc je suis bien sur une base EL8, ce qui est officiellement pris en charge.Cependant, lors de la configuration du dépôt j’ai eu cettre erreur :https://packages.centreon.com/rpm-standard/24.10/el8/x86_64/repodata/repomd.xmlMerci de me confirmer si les dépôts EL8 pour Centreon 24.10 sont bien disponibles et fonctionnels. Sinon, dois-je utiliser Centreon 24.04 en attendant ? 

Bonjour,Sur une derniere version 23.10 j’ai continuellement l’erreur suivante sur mon collecteur:ERROR - [core] Package 'gorgone::modules::core::action::hooks' already loadedJ’ai tenté de supprimer ces 5 dernieres lignes dans le 40-gorgone.yaml du collecteur mais rien y fait Merci pour vos retours

Hello,My cisco C3850 switches are attached to the Net-Cisco-Standard-Environment-SNMP-custom model.Centreon display these WARNING for some switches:Temp Inlet Sensor 0/1012' is 29 C Temp Inlet Sensor 0/1012' is 30 CTemp Inlet Sensor 0/3012' is 31 CTemp Inlet Sensor 0/1012' is 20 C Temp Inlet Sensor 0/3012' is 31 CRegarding the temperatur, the color should be green and not orange. How to solve it please?Maybe I have to exclude the Temp Inlet Sensor filtering it  in EXTRAOPTIONS of the Net-Cisco-Standard-Environment-SNMP-custom model but I don’t know the syntax.Hare are the current content of the EXTRAOPTIONS:--verbose  --filter-perfdata='^(sensor\.(celsius_|rpm_)|temp_)' Thank fo your help. Regards

Hi,We are using Centreon Open Tickets (Version centreon-open-tickets-21.10.1-1).It has been configured with rules to create ticket on our Jira infra.Afiter follwowing this documentation : Integration Open-Tickets - Accueil DIS - Centreon - Wiki (vaudoise.ch)… we can now open a ticket manually  from the’Custom View’ page… this iw working Well. But now we would like that tickets are created automatically when a Centreon Services reaches it critical hard State.To do this, I need to configure a Notification Command : but its means that we must to know the syntax on how to create a ticket in command line.On our poller we installed this package:centreon-plugin-Notification-Centreon-Opentickets-Api-20221017-094659.el7.centos.noarchIt provides this plugin : ‘/usr/lib/centreon/plugins/centreon_notification_centreon_opentickets_api.pl’ The modes availables are .   close-host   close-service   open-host   open-service … So we should be able to create a ticket in command line with this plugin, but

Hello,i follow the procedure to register remote server to central server and it exits with success: But on the central GUI, i’m not found the remote server preregistred, do you know  why???Thank for your help   

Hello everyone I”m monitoring hosts from a certain poller x that’s connected to the centreon central, however when i run command checks on the poller server I do get a result returned but on centreon web UI I see “uknown” state? and that no result was returned from plugin? anyone has any idea why? on the server itself:it’s same exact command so I’m unsure why I’m not seeing result on web UI?

Hi,I have installed centreon_fortinet_fortigate.pl fro the Monitoring connector manager.In the available mode I have uptime listed./centreon_fortinet_fortigate.pl --plugin=network::fortinet::fortigate::snmp::plugin --list-modePlugin Description: Check Fortinet Fortigate in SNMP....Modes Available: ap-usage cluster-status cpu disk hardware interfaces ips-stats link-monitor list-interfaces list-link-monitors list-switches list-virtualdomains memory sdwan sessions signatures switch-usage uptime vdom-usage virus vpnHowever when I try it:> /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl --plugin=network::fortinet::fortigate::snmp::plugin --mode=uptime --hostname=X.Y.Z.A --snmp-version='2c' --snmp-community='dummy'UNKNOWN: Cannot load module --mode. Can't locate snmp_standard/mode/uptime.pm in @INC (you may need to install the snmp_standard::mode::uptime module) (@INC contains: /usr/lib/centreon/plugins FatPacked::94775752674704=HAS

HelloMy company has a VM with Centreon setup (I think he himself is connected to other instances and getting their informations)I’m exporting this data into my VM with graphite (to visualize with Grafana) but not every host is showing in the DB.  (there is like 20 host out of 100 so lots of missing data)There is already an equivalent to my VM, an old setup by someone else and it is getting every host and dataSomeone has any idea what i could do / check ? additionnal info :graphite is running the whisper/carbon pair to receive and store datacarbon is listening to port 2003 in TCP (plaintext protocol)

Hello I’ve upgrade my old CentOS7 with Centreon 22.04 to OL8 with Centreon 24.I had to remove all mariadb, and centreon package to proceed the OS upgrade.The database is now correctly configured, I have my old data, and want to make the Centreon Upgrade.When I goes to page /install/upgrade, and start upgrade, I’m currently stuck at step 4: 22.10.30 to 23.04.0When I check logs I see some errors:sql-error.log>[2025-06-06T15:14:01+02:00] ERROR : [CentreonDb] Error while executing the simple query: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'sat.token_type' in 'where clause' | {"context":{"default":{"back_trace":{"file":"/usr/share/centreon/www/class/centreonDB.class.php","line":947,"class":null,"function":null},"request_infos":{"url":null,"http_method":null,"server":null,"referrer":null}},"exception":{"exception_type":"PDOException","file":"/usr/share/centreon/www/class/centreonDB.class.php","line":342,"code":"42S22","message":"SQLSTATE[42S22]: Column not found: 1054 Unknow

Good morning,we are trying to set up SAML authentication with our EntraID applicationWe´ve published application, we´ve remote login url, entity id and user id attributeBut when we try to login appears the following error: Authentication method 'X509, MultiFactor, X509Device' by which the user authenticated with the service doesn't match requested authentication method 'Password, ProtectedTransport'How can we fix it?

Hello,I am using centreon 24.10.6.I have created recurring downtimes on certain services (as seen below), however they do not work and do not show up in Monitoring>Downtimes. On the server itself, manipulating recurring downtimes do not generate any logs anywhere, however it does affect the database and I can see the different entries. When creating regular downtimes however, it does work normally, showing up in the Monitoring section and in the logs on the server. It might be a problem with rights on certain files as I’ve been having problems with that recently or that the process which is supposed to retrieve information from the database is not functional, but I haven’t been able to figure it out.  Thank you !

BAM update from 23.10 to 24.10 does not seem to apply required SQL schema updates, as a result upgrade renders BAM unusable with error like this[2025-04-07T14:32:23+03:00] ERROR : [CentreonDb] Error while using CentreonDb::query | {"context":{"default":{"back_trace":{"file":"/usr/share/centreon/www/class/centreonDB.class.php","line":947,"class":null,"function":null},"request_infos":{"url":"/centreon/api/internal.php?object=centreon_bam_top_counter&action=getBamTopCounterData","http_method":"GET","server":"10.204.72.72","referrer":"https://10.204.72.72/centreon/main.php?p=20201"}},"exception":{"exception_type":"PDOException","file":"/usr/share/centreon/www/class/centreonDB.class.php","line":1011,"code":"42S22","message":"SQLSTATE[42S22]: Column not found: 1054 Unknown column 'all_business_views' in 'field list'","previous":null},"custom":{"db_name":"centreon","query":" SELECT ba_group_id, all_business_views FROM mod_bam_acl ","pdo_error_infos":["42S22",1054,"Unknown column 'all_b

🇬🇧Hello,I have a VMWare probe "Datacenter Alarm Custom" configured on a VCSA. When I encounter an issue reported by the vCenter, I get all the details in the resource status:Statut détailléCRITICAL: Datacenter 'DCXXXXXX' 1 problem(s) detectedchecking datacenter 'DCXXXXXX'critical: alarm [red] [VirtualMachine] [XXXXXXXXX] [2025-04-08T13:33:26.854728Z] Virtual machine CPU usage/Default alarm to monitor virtual machine CPU usage This is perfect, but I would like to receive this content via email as well, especially in case of anomalies at night or any other time when I am not in front of the monitoring system. However, the history does not mention the details nor the email notifications:mardi 8 avril 2025 15:07CritiqueTentatives: 3CRITICAL: Datacenter \'XXXXXXXX\' 1 problem(s) detected ***** centreon Notification *****Notification Type: PROBLEMService: Datacenter-AlarmsHost: XXXXXXXXAddress: 123.45.67.89State: CRITICALDate/Time: 08-04-2025 Additional Info : CRITICAL: Datacenter XXXXXXXX

Hello,I am using centreon 24.10.6.I’ve had all servers up and running for a while now and I’ve noticed that there are some gaps in the Availability page in the Reporting tab. Most recently I noticed a gap of more than a week where the status is written as “Undetermined” even though the servers were in fact up and the checks were still running without issue and without change (seen in logs).Although I could take the Mean Time percentages, I’d rather have the graph display the correct values. I’ve tried rebuilding for these dates and it executes without error but doesn’t change anything. /usr/share/centreon/cron/eventReportBuilder --config=/etc/centreon/conf.pm --start-time="2025-05-25" --end-time="2025-06-05" --rebuild The conf.pm file is correctly configured.This is the output of the rebuild command:  I wasn’t able to find the issue, if you have any idea please let me know, thank you !

Hi,One of our remote server centreon_storage tables are not partitioned properly. all tables below.My question is, what is the best approach to fix the issue?Should I try to use this on the docs? https://docs.centreon.com/docs/administration/database-partitioning/Or Do I need to re-create the centreon_storage DB?Also noticed that data_bin table is already partitioned​ into one.​​​​​​-rw-rw---- 1 mysql mysql 479606079488 May 20 15:41 data_bin#P#pmax.ibd Thank you in advance for the suggestions.  

I am trying to monitor some devices with snmp traps. I have followed the centreon docs and I receive the trap, but I don´t know why it is not working.  I have configured a debug and I config that I receive the trap, but I don´t know why folder /var/spool/centreontrapd/ is always empty. Please if you could help me I would really appreciate that.Here is my config: [root@CENTREON2025 ~]# more /etc/snmp/snmptrapd.confdisableAuthorization yestraphandle default su -l centreon -c "/usr/share/centreon/bin/centreontrapdforward"OPTIONS="-On -Lf /var/log/snmptrapd.log -p /var/run/snmptrapd.pid"-----------------------------------[root@CENTREON2025 ~]# more /etc/centreon/centreontrapd.pmour %centreontrapd_config = (        spool_directory => '/var/spool/centreontrapd/',        # databases credentials        centreon_db => "dbname=/etc/snmp/centreon_traps/1/centreontrapd.sdb",        centstorage_db => "dbname=/etc/snmp/centreon_traps/1/centreontrapd.sdb",        db_type => 'SQLite',     

Getting 'No output returned from plugin' alert on Windows Server. The server is reachable (pingable) from the poller, but all services are showing an 'Unknown' status.

Bonjour, Nous sommes actuellement entrain de tester une version dev de Centreon pour une montée de version. Nous souhaitons utiliser la fonctionnalité d’authentification SAML, pour cela devons nous configurer Centreon dans notre fournisseur d’identité (Google dans notre cas) ? Autre chose dans le champ remote login URL, qu’est ce qui est exactement attendu ?  Merci d’avance pour les réponses  Cordialement 

Bonjour,Je souhaite monitorer un partage CIFS via le plugin centreon_plugins.pl --plugin apps::protocols::cifs::plugin --mode connectionJ’utilise la commande suivante :/usr/lib/centreon/centreon-plugins/src/centreon_plugins.pl --plugin apps::protocols::cifs::plugin --mode connection --hostname=mon_serveur --cifs-username=’mon_utilisateur’ --cifs-password=’mon_mot_de_passe’  --directory='mon_partage'La commande en putty fonctionne très bien avec l’utilisateur centreon-engine mais dès que je l’implémente dans Centreon j’ai le message permission denied.J’ai réalisé le test de copier la commande depuis Centreon vers la console et la commande fonctionne bien.Merci pour vos suggestions.

Hello, I need help figuring out how to exclude data from a service.I'd like to hide the "Hole Punch Box" from monitoring the "MarkerSupply-Usage" service.To do this, I was thinking of using the EXTRAOPTIONS --filter command. However, I can't find the right syntax for this to work properly.I've tried a lot of different things, e.g.:--filter '^(?!Hole Box Punch$)'--filter '.*Cart.*'Do you have any ideas, please? Thanks for your help.

Hello,I already had a remote server in CentOs7I reinstalled a new server in Alma 9 and when trying to put it into service I had this problem.The remote server is "Not Running" only on itself, but appears online on the central server.Central:Remote server:  The communication works because when I restart the remote I can see the uptime updating on the central.I checked all my services they are up: CBD, centre-engine, centreon, gorgoned, centreontrapd By checking in /var/log/Centreon-broker with the “poller-broker.log” file I have this error message: [warning] Poller '' with id 0 already known as connected. Replacing it with '' [tcp] [error] TCP: Connection refused to central:5669 [tcp] [error] Error while reading on socket from central: Operation canceled [tcp] [error] TCP: Connection refused to localhost:5670

Bonjour,Hier matin en supervisant mes imprimantes, je parviens à faire fonctionner les services de ces hôtes, mais malgré le fait que les ping soient fonctionnels pour une majorité d’appareils, l’interface web me dit toujours que mes appareils sont dans un état de pending, donc en attente d’être validé soit 24 heures après l’ajout de tous ces hôtes.Merci pour vos réponses.