Centreon Infra Monitoring

In my production Centreon server has more than 100K services and I need to send only selected service metrics to Graphite. I’ve tried with Centreon Stream Connector LUA file. but due to heavy count of metrics, process is getting queue. Can someone give me hint to resolve this. 

Hi,we have Centreon 24.10 installed, we want to export the data to graphite, we followed below steps :https://www.centreon.com/export-data-graphite/but centreon metrics don’t appear on Graphite interface! Please help 

HelloI’m encountering an issue for a new firewall I have to monitor (a fortinet)i’m using the autodiscover rule for the traffic interface, unfortunately there are some interace named with an invalid character for centreon : &I get discover results like traffic-WAN-AT&T  or “lan-R&D” you can’t change the name in the firewall unless you destroy and recreate the interface, so it’s not possible to do that (for now) is there a way in the autodiscover rule to make some regex magic to delete the “&” from the name, I looked around the discover rules, you can do complex thing in this advanced sectionwhere you can manipulate the strings, but i’m stuck on what to put here for simply deleting all the invalid character (or replacing them with something like dash “-”) an example I found what the exact opposite for extracting the windows drive letter and reusing it in the service name (disk-C, disk-D, etc… from an old kermit article Découverte auto des disques | Les archives de Kermit

Bonjour,J’ai un problème quand j’utilise le plugin “os::linux::local:plugin” avec le mode “memory”.Quand j’ajoute plusieurs Tresholds et qu’ils sont en warning ou critical le output est en doublon :commande :/opt/nagios/libexec/centreon_plugins.pl --plugin=os::linux::local::plugin --mode=memory --warning-memory-usage-prct=95 --critical-memory-usage-prct=98 --warning-memory-free-bytes=1000000000: --critical-memory-free-bytes=500000000:résultat :WARNING: Ram total: 34.36 GB used (-buffers/cache/slab): 33.65 GB (97.96%) free: 717.19 MB (2.04%), Ram total: 34.36 GB used (-buffers/cache/slab): 33.65 GB (97.96%) free: 717.19 MB (2.04%) | 'memory.usage.bytes'=36136423424B;;;0;36888453120 'memory.free.bytes'=752029696B;1000000000:;500000000:;0;36888453120 'memory.usage.percentage'=97.96%;0:95;0:98;0;100 'memory.buffer.bytes'=0B;;;0; 'memory.slab.bytes'=291487744B;;;0;Comme on peut le constater, j’ai 2 fois la ligne :Ram total: 34.36 GB used (-buffers/cache/slab): 33.65 GB (97.96%) free: 717.19

I can no longer connect to my Centreon MAP server from my thick client. I feel like I'm entering the correct credentials, but each time the "Could not send Message" notification appears. I would like to know where I can find my login / password and how can I reset them ?

Hello,I want to use http collection to query the Redhat Ansible Automation Platform API.To authenticate, I first need to retrieve the cookies from this request:[root@107501lctm collection-config]# curl -c - https://console.aap-organismes.hp.cnp.ramage/api/login/ -v*   Trying 55.245.223.47...* TCP_NODELAY set* Connected to console.aap-organismes.hp.cnp.ramage (55.245.223.47) port 443 (#0)* ALPN, offering h2* ALPN, offering http/1.1* successfully set certificate verify locations:*   CAfile: /etc/pki/tls/certs/ca-bundle.crt  CApath: none* TLSv1.3 (OUT), TLS handshake, Client hello (1):* TLSv1.3 (IN), TLS handshake, Server hello (2):* TLSv1.3 (IN), TLS handshake, [no content] (0):* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):* TLSv1.3 (IN), TLS handshake, [no content] (0):* TLSv1.3 (IN), TLS handshake, Certificate (11):* TLSv1.3 (IN), TLS handshake, [no content] (0):* TLSv1.3 (IN), TLS handshake, CERT verify (15):* TLSv1.3 (IN), TLS handshake, [no content] (0):* TLSv1.3 (IN), TLS

Bonjour , je suis nouveau dans l'utilisation de centreon. Je souhaite la tester pour la déployer chez 1 client si elle fonctionne .je rencontre 1 problème pour me connecter au serveur afin d'accéder à la page de configuration. je suis sur la version 23h10 sur VMware (format machine virtuelle). Quand je me connecte avec mon ip ; admin/ Centreon!123 ça ne fonctionne pas . Ensuite j'ai le message utilisateur bloqué .une autre question: Comment mettre l’ip en fixe ? Merci d'avance pour votre aide .

Hello,Do you have any documentation for use HashicorpVault with centreon_vmware daemon ?Sebastien

helloI got an appliance (fortinet analyzer) that has a snmp capability, it works fine for basic system info like cpu, nic and storage, but for the memory it uses the same mib as the storage and it is filtered  here is an extract of the snmpwalk, the ram and swap are in the hrStorage* tables along with the hard drivesHOST-RESOURCES-MIB::hrMemorySize.0 = INTEGER: 8161580 KBytesHOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1HOST-RESOURCES-MIB::hrStorageIndex.2 = INTEGER: 2HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3HOST-RESOURCES-MIB::hrStorageIndex.4 = INTEGER: 4HOST-RESOURCES-MIB::hrStorageType.1 = OID: HOST-RESOURCES-TYPES::hrStorageRamHOST-RESOURCES-MIB::hrStorageType.2 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemoryHOST-RESOURCES-MIB::hrStorageType.3 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDiskHOST-RESOURCES-MIB::hrStorageType.4 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDiskHOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: Physical MemoryHOST-RESOURCES-MIB::hrStorageDescr

Hello,Since last week my Centroen doesn’t work, I checked all file in /var/log/centreon* and i don’t have any clue for the database issue. The only one that I get are :MySQL error : cannot connect to database 'mysql:host=localhost:port=3306;dbname=centreon': Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2) (caller: gorgone::class::db:/usr/share/perl5/gorgone/class/db.pm:342) (try: 0)and pe":"PDOException","file":"/usr/share/centreon/www/class/centreonDB.class.php","line":147,"code":2002,"message":"SQLSTATE[HY000] [2002] No such file or directory","previous":null},"custom":{"db_name":"centreon","pdo_error_infos":["HY000",2002,"No such file or directory"],"pdo_error_code":2002,"dsn_mysql":"mysql:dbname=centreon;host=localhost;port=3306"}}}[2025-04-08T10:58:29+02:00] CRITICAL : [CentreonDb] Unable to connect to database : SQLSTATE[HY000] [2002] No such file or directory | {"context":{"default":{"back_trace":{"file":"/usr/share/centreon/www/class/centreonDB.class.

Hello, I’m encountering an issue when trying to retrieve the ID of a host category using the following API route: {{baseUrl}}/configuration/hosts/categories?search={"name":"X"} If the host category X is not linked to any host, the API returns an empty result. However, if I don’t use the search parameter, the API lists all my categories — including the one named X, even if it’s empty. My goal is to retrieve the ID of this category to use it in another script. As a workaround, I can fetch all categories without using the search parameter and then filter the results manually, but that requires handling pagination and parsing the entire result set, which is not ideal. I don’t understand why the category is returned when calling the endpoint without search, but not when using the search filter. To me, this behavior could be considered a bug. Has anyone experienced this before, or does someone have more information on this? Thanks in advance!

I am installing a distributed architecture for my centreon.I have a central centreon and I need to install a remote server on it (maybe in Proxy mode) and finally pollers in different locationsThe IP addresses of the central server, remote server and pollers are in different network ranges and are connected by VPNs. The VPNs allow traffic on all ports from Central to Remote and from Remote to Poller.this would be the architecture I have followed the steps in this post. But I have checked everything and I can't detect the problem.On the server I have this error in /var/log/centreon-gorgone/gorgoned.log2025-03-07 13:35:12 - DEBUG - [proxy] skip node pull target '223' for node '223' - never connected2025-03-07 13:35:12 - DEBUG - [proxy] no pathway for target '223'2025-03-07 13:35:12 - DEBUG - [proxy] skip node pull target '223' for node '223' - never connected2025-03-07 13:35:12 - DEBUG - [proxy] no pathway for target '223'Can anyone help me?THX

I’m trying to migrate an old Centreon 19.10.23 running on CentOS7 to 24.04 running on almalinux 8.I have followed the procedure here : https://docs.centreon.com/fr/docs/migrate/migrate-from-el-to-el/The problem occures during the web upgrade : 20.04.18 to 20.04.19    There is no active transactionIn the sql-error.log :2024-08-22 14:00|0|0|TokenRemoval CRON: failed to delete old tokens2024-08-22 15:00|0|0|Deleting expired refresh tokens2024-08-22 15:00|0|0|SQLSTATE[42S02]: Base table or view not found: 1146 Table 'centreon.security_authentication_tokens' doesn't exist QUERY : DELETE st FROM security_token stWHERE st.expiration_date < UNIX_TIMESTAMP(NOW())AND EXISTS (    SELECT 1    FROM security_authentication_tokens sat    WHERE sat.provider_token_refresh_id = st.id    AND sat.token_type = 'auto'    LIMIT 1) This table does not exist.I tried to use the solution proposed here :to create the missing tables. it works fine for security_token but there’s an error when I try to create sec

I no longer have access to my administration platform

Hello,I have a problem on a Plugin apps::vmware::vsphere8::esx::plugin/usr/lib/centreon/plugins/centreon_vmware8_esx_restapi.pl --plugin=apps::vmware::vsphere8::esx::plugin --mode=power --hostname='******' --port='443' --proto='https' --esx-id='****' --username='*****' --password='*****'UNKNOWN: Undefined subroutine &centreon::plugins::misc::is_empty called at /usr/lib/centreon/plugins/centreon_vmware8_esx_restapi.pl line 839. Here's the result. Regardless of the mode, the result is always the same. FYI, I have the latest version of the plugin: centreon-plugin-Virtualization-Vmware8-ESX-Restapi-20250400-1.el9.noarchthanks you

Hi, new user here. We have deployed a centreon server only a couple of days ago and I’m trying to figure out if it covers all our needs.In particular I was tinkering with templates but seems that doesn’t work as I was expecting. I’ve created a host template with all the basic settings we need: notifications, services templates, scheduling…Now when I try to create a new host and assing this template to it, new host is inheriting only services and icon, no other fields are copied from the template.Is that supposed to work like this or I’m missing something? Thanks in advance for your attentionAlessio

Hello community o7 ! I am struggling with how to correctly write logfile name, here’s the command I tried with :  bash-5.1$ /usr/lib/centreon/plugins//centreon_nsclient_restapi.pl --plugin=apps::nsclient::restapi::plugin --mode=query --hostname='X.X.X.X' --port='8443' --proto='https' --legacy-password='XXXX' --ssl-opt="SSL_verify_mode => SSL_VERIFY_NONE" --timeout=60 --command=check_logfiles --arg='--logfile="C:/Program Files/Centreon NSClient++/nsclient.log" --tag="" --criticalpattern="" --warningpattern="" ' --debugI’ve tried with differents separators : /, \, //, \\, \/, /\ but everytime I get this error message :  Failed to execute check_logfiles: 2: The specified file cannot be found.======> request sendGET https://X.X.X.X:8443/query/check_logfiles?--logfile%3D%22C%3A%2FProgram%20Files%2FCentreon%20NSClient%2B%2B%2Fnsclient.log%22%20--tag%3D%22%22%20--criticalpattern%3D%22%22%20--warningpattern%3D%22%22%20[...]{"header":{"source_id":""},"payload":[{"comm

Hello everyone,I'm facing an issue while trying to use the severity level to create a ticket with a priority level in our custom ITSM system. Here's the approach I've followed so far:I've created a severity field within the categories. However, I'm stuck on the following points: It's not possible to retrieve the severity level directly from the service or host in a macro within the notification command. It's not possible to retrieve this information via command line (CLAPI v1) or REST API v1. This is preventing the creation of the ticket with the correct priority based on the severity.I'm wondering if anyone has any ideas or solutions to resolve this.I considered creating a special macro on all hosts/services, but I would prefer to use the existing setup as it is already 

Bonjour,pour un besoin particulier j’ai configuré des sondes DSM rattachées à un host.Dans la conf DSM j’ai service template base qui est un service passif, dans lequel est défini une commande et un check freshness afin de libérer les slots pour de nouvelles alarmes et éviter qu’elles ne s’empilent en DB. Le check freshness n’est pas lancé toutes les 30s comme attendu.Bien évidemment j’ai modifié la durée du clean_locks_time et clean_locks_keep_stored dans centreon_dsmd.pm à 10s chacun.centreon-dsm-client-23.10.3-1.el8.noarchcentreon-dsm-server-23.10.3-1.el8.noarch Mon souci est que je ne peux pas mettre les services en actifs, car ils me servent à voir si une interco avec des produits tiers envoyant leur messages a Centreon est fonctionnelle en se basant sur le “last check”. Si les sondes sont lancées d’elles mêmes toutes les minutes

Hello,I just recreated a new fresh install of centreon, I just clicked on option “login the panel : And I cannot access anymore to my web page

Bonjour, J’ai récemment installé Centreon sur une debian 12. L’installation s’est faite “correctement” avec la commande : curl -L -s https://download.centreon.com/24.10/unattended.sh | bashCependant je rencontre un problème, mon collecteur “Central” ne veut pas passer dans l’état “En cours d’exécution”. J’ai suivis les docs d’installation officielles de Centreon, les différents forum, etc… Mais rien n’a fonctionné. Même au niveau de ma debian, je n’ai touché à aucun fichier de conf.  Si quelqu’un à une solution, je suis preneur ! 

Hi,We just updated to the version 24.10.2, and started to use the dashboards just now, we were (and are) still using custom view for most of our issues We created a dashboard for our services, and we can see that the aknowledged ones appear in the grid view, and I can’t find a workaround to get rid of them. I found this post for the previous version (problem with the 24.4.4, patched in 24.4.5) I looked around in the new DbReadResourceRepository.php file, it look like the filter is already set to resources.enabled = 1 (lines 184 and 462), but aknowledged services still show in the view.  I’m not against a workaround if there is no solution yet, I didn’t found a related issue in the recent posts (24.10 and up), but thanks to anyone that can help us start with those dashboard views =)   

Hello , I try to install another one Remote Server on Azure.Following Centreon doc , it’s impossible im stuck on step 7 during install . I tried to reinstall all but always the same pbm .Any ideas ?

I dont know why, I have a centengine error, I get the following output when I put systemctl status centengine: centengine[38831]: [date] [configuration] [info] Processing object config file '/etc/centreon-engine/severities.cfg'centengine[38831]: [1674206969] [38831] Reading resource file '/etc/centreon-engine/resource.cfg'centengine[38831]: [date [configuration] [info] Reading resource file '/etc/centreon-engine/resource.cfg' centengine[38831]: [date] [core] [info] Starting the TCP thread pool of 4 threadscentengine[38831]: [date] [core] [info] protocols: registering protocol ('file' (layers 1-3)centengine[38831]: [date] [core] [info] protocols: registering protocol ('compression' (layers 6-6) centengine[38831]: [date] [core] [info] protocols: registering protocol ('BBDO' (layers 7-7)centengine[38831]: /usr/sbin/centengine: symbol lookup error: /usr/lib64/nagios/cbmod.so: undefined symbol: _ZN3com8centreon6broker3neb9log_entryC1Evsystemd[1]: centengine.service: Main process exited, cod

########## FRENCH ###########Bonjour,Le 25 Novembre dernier, j'ai effectué une montée de version Centreon vers la version 24.10 .Depuis ce jour, l'historique de mes sondes est arrêté en date du 25 novembre....Quelqu'un pourrait m'aider à debug et remédier à ce problème s'il vous plait ?########## ENGLISH ##########Hello,On November 25th, I upgraded Centreon to version 24.10 .Since that day, the timeline of my services is stopped as of November 25th....Could someone please help me to debug and remedy this problem?  Captude du 19/12/2024 // image taken on 12/19/2024