Unanswered questions

Bonjour,Je cherche à ouvrir des tickets dans mon ITSM (EasyVista) via OpenTicket, mais je rencontre une difficulté avec les macros.Je souhaite passer en paramètre le Catalogue GUID stocké dans la macro EVSM_CATALOG_ID située dans les modèles (templates) de mes services. Lorsque je renseigne le GUID directement dans la règle de notification (champ Catalog GUID), cela fonctionne. En revanche, si j'utilise la variable {$service.custom_variables.EVSM_CATALOG_ID}, la transmission échoue. De plus, je souhaiterais récupérer la valeur présente dans l'alias du service pour l'intégrer dans le champ CI, afin de lier automatiquement le ticket à ce CI.Pourriez-vous m'aider à résoudre ces deux points ?Merci d'avance.English Version  Hello,I am trying to open tickets in my ITSM (EasyVista) using OpenTicket, but I am having an issue with macro integration.I need to pass the Catalog GUID as a parameter. This GUID is stored in the EVSM_CATALOG_ID macro within my service templates. When I enter the GUI

Hello everyoneI tried to update centreon 23.04.2 to 23.04.7, I done the update without problem but after this pollers are not running.Someone had this issue ?I followed this topic, no result https://thewatch.centreon.com/platform-7/pollers-and-central-not-running-after-upgrade-from-21-04-to-21-10-505?postid=1623#post1623  /var/log/centreon-broker/central-broker-master.log  

Hello, Since the update from 24.10.15 to 24.10.18, the graph date picker is broken on our instance.Quick time ranges like “Last 3 hours” are working normally but if we want to zoom on a graph or set a manual time range, it fails 100%. The issue comes from the Javascript not selecting the right start/end date for the API call. In browser console we’ve got messages like :moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 09:48. See http://momentjs.com/timezone/docs/#/data-loading/.moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 10:24. See http://momentjs.com/timezone/docs/#/data-loading/.moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 09:48. See http://momentjs.com/timezone/docs/#/data-loading/.moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 10:24. See http://momentjs.com/timezone/docs/#/data-loading/.d3.min.js:1 Error: <rect> attribute x: Expected length, "NaN".d3.m

I downloaded the VMware version 25.10.deb12.standard-1766075705.ovaI then followed these instructionshttps://docs.centreon.com/docs/installation/installation-of-a-central-server/using-virtual-machines/Unfortunately, despite this I cannot connect with a web browser.I can ping the ip address but I also cannot ssh onto the server with puttyFells like I am missing some instructions

I've been asked to produce a report on the average memory use of our servers.I can get the information I need via a Performance Graph (see below) but, because I've beenasked to do this for several hundred servers, I'm looking for a way to automatethis as much as possible.Is it possible to get average memory use via clapi or SQL queries? Memory use on one server 

Hi,When “Detection by browser” is selected, and while my browser is set to en_US, there are numerous part in the UI that are still displayed in French.It’s ok (ie: all is displayed in English) if I set “en_US” in my Centreon profile.

Hi,I migrated Centreon from 23.10 to 24.10.17 on January 22. I've been notified of a problem with the export, which no longer works in Customviews.For example, export from a service-monitoring :/var/log/php-fpm/centreon-error.log[09-Feb-2026 10:35:16 UTC] PHP Warning: Undefined variable $db in /usr/share/centreon/www/widgets/service-monitoring/src/export.php on line 443The rest of the interface works fine.I have a development platform with the same version number on which I cannot reproduce the problem. It works fine.Anay idea ?

Hello,Are there any checks available to verify:See for a check on the status of managed devices (synchronised/conflict, etc.) (Fortimanager) For storage, see for provisioning monitoring and an alert above 80% (ESX)  

Est-il possible d’utiliser le magasin d’autorités de certification Windows plutôt que de devoir spécifier un chemin vers un fichier de certificat en dur ?Les autorités de certification étant déjà déployées sur mes serveurs via des GPO, il serait pertinent de pouvoir s’appuyer sur ce mécanisme existant plutôt que de maintenir des fichiers séparés.  Is it possible to use the Windows Certification Authorities store instead of specifying a hard-coded path to a certificate file?Since the certification authorities are already deployed to my servers via Group Policy, it would make sense to leverage this existing mechanism rather than maintaining separate certificate files.

J’ai fait mes tests en NO TLS et toutes mes commandes de vérifications marchaient mais dès lors que je passe en TLS insecure, toutes mes commandes de vérifications passent en “Host {...} is down” et ma commande de vérification de l’hôte elle passe en execute command failed (OS-Windows-Centreon-Monitoring-agent-Host-Alive). Pourtant voici ce que me remontent les logs sur l’hôte : [2026-02-17 10:57:57.894] [centreon-monitoring-agent] [info] [main_win.cc:219] centreon-monitoring-agent start[2026-02-17 10:57:57.895] [centreon-monitoring-agent] [info] [streaming_server.cc:174] create grpc server listening on 0.0.0.0:4317[2026-02-17 10:57:57.895] [centreon-monitoring-agent] [info] [grpc_server.cc:57] encrypted server listening on 0.0.0.0:4317 cert: -----BEGIN..., key: -----BEGIN..., ca: ....[2026-02-17 10:57:57.898] [centreon-monitoring-agent] [debug] [grpc_server.cc:89] server default compression deflate[2026-02-17 10:57:57.898] [centreon-monitoring-agent] [debug] [grpc_server.cc:99] server

Hi, I’ve recently installed a mediawiki server and configured in the Centreon settings.But when I look in the cron logs I can see :root@STR-PRD-L-CEN01:~# tail /var/log/centreon/knowledgebase.logWiki is not configured. You can disable cron in /etc/cron.d/centreon for wiki synchronization.Wiki is not configured. You can disable cron in /etc/cron.d/centreon for wiki synchronization.In the database, I can see the rights settings :MariaDB [centreon]> SELECT * FROM options WHERE options.key LIKE 'kb_wiki%';+---------------------+--------------------------------------------+| key                 | value                                      |+---------------------+--------------------------------------------+| kb_wiki_password    | ****************                    || kb_wiki_url         | https://centreon.********/mediawiki/ || kb_wiki_account     | centreon                                   || kb_wiki_certificate | 1     So, I have an issue with the links synchronisation between the Ce

Hello,I want to change some common services using the “mass change” option with the “replacement”.When applying the new config, I get a blank page.Appache error.log display the following error when applying the config :[Fri Feb 20 11:53:57.636143 2026] [proxy_fcgi:error] [pid 373731:tid 373731] [client XXXXXXXXX:1111] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught InvalidArgumentException: The command ID does not exist. in /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php:2711\nStack trace:\n#0 /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php(1608): updateService_MC()\n#1 /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php(1536): updateServiceInDBForOnPrem()\n#2 /usr/share/centreon/www/include/configuration/configObject/service/formService.php(1187): updateServiceInDB()\n#3 /usr/share/centreon/www/include/configuration/configObject/service/serviceByHost.php(108): require_once('...')\n#4 /

Hi All.We are using HP Systems insight manager as snmp trap receiver. The way it handles them is quite simple : when a trap is received and if it’s severity is above informational (configurable), an alert is sent and logged with the sending host. Of course the host must be declared first. If the OID is unknown, it logs it with the host too, so we can see that a MIB is missing. Simple and efficient. But it’s no longer supported and it’s missing some functionalities like the most secure SNMP v3 encyption levels.So I’m looking at moving the trap management to Centreon.I’ve read many documents and post and my (simplified) understanding is that with Centreon we must attach a SNMP service to a host and define the traps it will manage.But for me there is a problem : if the host sends a trap that is not monitored by the service, then I won’t be warned.Is my understanding correct ?If yes, is there the possibility to do the following : declare a SNMP service for a host and say : whatever the snm

Hello, i upgrade this morning in 25.10.8, i have all my snmp metric in error… When i try in command line : I see : --snmp-community='encrypt::encryptchain” i have a UNKNOWN: SNMP GET Request: TimeoutWhen I replace 'encrypt' with the name of my unencrypted community, I get“OK: Ram Total: 7.57 GB Used (-buffers/cache): 733.53 MB (9.46%) Free”Thank you in advance; most of my metrics are malfunctioning.Best regards 

Hello everyone,I have a question regarding the X509 Certificate check (https://docs.centreon.com/pp/integrations/plugin-packs/procedures/applications-protocol-x509/)I’m wondering if its possible to check the whole chain of certificate ?The situation is as follow :ROOT → CA → CERTThe Root is still OK The CA cert is expired The Cert is OK (but signed with a expired certificate)The usecase is when we are using deepssl.So that’s mean we will never see the cert in CRITICAL status, but only when the CA will be expired.UNKNOWN: Error creating SSL socket: , SSL error: SSL connect attempt failed error:0A000086:SSL routines::certificate verify failed I’m now wondering if we can monitor the whole cert chain for a website and see if the date is near (30 days for example) for the CA and ROOT ?Thanks ! 

I’ve installed a fresh server Debian 12 with Centreon 25.10But  the Custom View is not listed with the Home entry.I only got the Dashboard entryIs there some option to activate this menuI’ve already checks the ACL

Hello all,I’m using Centreon Autodiscovery and i want to improve my hosts information automatically.For example : I use CISCO MERAKI and the result of one them is like : from this , it could be great for me to use the URL value in “action URL” in “host extended infos” tab in host configuration, mac address in “note” field … so create one property per information… or adding some value directly in custom macros.Is it possible ? if yes how ?

Voici une version adaptée intégrant ce contexte : Bonjour à tous,Nous supervisons actuellement des conteneurs OpenVZ avec Centreon.Nous disposons d’un ancien plugin “fait maison” qui permet de contrôler l’état des conteneurs (notamment la partie démarrage), mais il commence à dater et nous souhaitons savoir s’il existe aujourd’hui une méthode plus standard / officielle pour superviser correctement cet aspect.Notre besoin est de : Détecter un échec de démarrage d’un conteneur Vérifier que le conteneur est réellement en état running Disposer d’un statut clair et fiable dans Centreon (OK / CRITICAL si le conteneur n’est pas démarré) Éviter de maintenir un script custom si une solution packagée existe Nous n’avons pas trouvé de plugin officiel Centreon Plugin Pack dédié à OpenVZ pour cette vérification spécifique.Existe-t-il : Un plugin officiel Centreon compatible OpenVZ ? Une bonne pratique recommandée (via SNMP, agent, API, commande système côté hôte) ? Un mode opératoire vali

BonjourJ’ai un problème avec l’autovacuum qui déclenche régulièrement la sonde querytime (--warning='180'--critical='360').En effet, le vacuum est dure souvent plus d’une heure sur certaines grosses tables.J’ai bien exclu le user “postgres” mais cela ne change rien puisque dans pg_stat_activity le “usename “ est null pour les workers du vacuum :postgres=#                   SELECT pg_database.datname, pgsa.*,                    COALESCE(ROUND(EXTRACT(epoch FROM now()-query_start)),0) AS seconds                FROM pg_database LEFT JOIN pg_stat_activity pgsa ON pg_database.datname = pgsa.datname AND (pgsa.query_start IS NOT NULL AND (pgsa.state NOT LIKE 'idle%' or pgsa.state IS NULL))                where COALESCE(ROUND(EXTRACT(epoch FROM now()-query_start)),0) > 10 ORDER BY pgsa.query_start, pgsa.pid DESC;  datname  | datid |  datname  |   pid   | leader_pid | usesysid | usename | application_name | client_addr | client_hostname | client_port |         backend_start         |        

HiWhen i want to add services on hosts, i have this message in centreon-error.log : PHP Fatal error:  Uncaught InvalidArgumentException: The command ID does not exist. in /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php:2123Stack trace:#0 /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php(1863): insertServiceForOnPremise()#1 /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php(1826): insertServiceInDBForOnPremise()#2 /usr/share/centreon/www/include/configuration/configObject/service/formService.php(1159): insertServiceInDB()#3 /usr/share/centreon/www/include/configuration/configObject/service/serviceByHost.php(108): require_once('...')#4 /usr/share/centreon/www/main.get.php(277): include_once('...')#5 {main}  thrown in /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php on line 2123 I use centreon 25.10.6, this case is not for all services. In that case, is when i want to add

Lorsque l’on met le service en downtime, les check sont toujours fait.Est-ce qu’il faudrait passer le service en mode passif ?Est-ce que l’option “disable service check when host is down” pourrais être également mis en place sur les downtimes ?

Hello,I want to monitor files on Windows and Linux:Filter on the most recent file pattern : *.csv critical si > 24hI have combed through the Centreon documentation but cannot find a solution. Do you have any ideas?Thank you,------------------------------------------------------------------------------------------------------------Bonjour,Je souhaite superviser des fichiers sur windows et linux :Filtrer sur le fichier le plus récent patern : *.csv critical si > 24hJ’ai épluché les docs centreon mais je ne trouve pas de solution. Avez-vous une idée ?Merci,

Hello,Somebody know a fresh project for have a notification per mail with html ?I see GitHub - mcinquin/centreon-notifications: New notifications for Centreon but it’s 9 years old.HTML/formatted Notification | Community stil in the backlog apparently ?Regards,B’

Since the last update,gorgoned logs rotation failed:2026-02-16T00:00:06.432442+01:00 central logrotate[510870]: error: gorgoned:9 unknown user '@USER@'2026-02-16T00:00:06.432518+01:00 central logrotate[510870]: error: found error in /var/log/centreon-gorgone/gorgoned.log , skipping2026-02-16T00:00:06.432543+01:00 central logrotate[510870]: error: found error in file gorgoned, skippingroot@central:/var/log/centreon-gorgone# cat /etc/logrotate.d/gorgoned/var/log/centreon-gorgone/gorgoned.log { copytruncate weekly rotate 52 compress delaycompress notifempty missingok su @USER@ @GROUP@}This behaviour occured on :Centreon 25.10.7 Debian Centreon 24.10.18 Alma Linux 8I changed “@USER@ @GROUP@” by “root root”

Hello everyone,I’m trying to monitor Proxmox VMs using Centreon with the Proxmox VE Rest API plugin. I’ve followed the official documentation as well as the steps described on these pages:Centreon Plugin Packs Documentation : https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-proxmox-ve-restapi/Proxmox VE Rest API Plugin Procedure : https://docs.centreon.com/docs/monitoring/pluginpacks/#checking-the-monitoring-procedureI’ve configured the plugin with the correct credentials and macros, but I’m facing two issues:When I run the plugin manually or through Centreon, I get the following error:UNKNOWN: 401 authentication failureI also installed the Proxmox VE connector directly from Centreon and configured my host using the provided template. However, when I check the host availability, it shows 100% undetermined.I’m wondering if this could be related to:the realm (pam vs pve),SSL settings,or something else.Another point: the VM.monitoring command no longer exis