Recently active topics

Bonjour,Suite upgrade en 26.10, nous venons de nous apercevoir que nous n’avions plus la possibilité de décrire les arguments dans les commandes Centreon.Est-ce une issue connue ? La méthode a t’elle évoluée ? Dans l’attente de votre retour.Corentin Launay

The application has had a full visual overhaul, released today. The interface now follows the Centreon design system and colours across every page, with a new logo, a new navigation bar, a new login page and redesigned emails, alerts and reports. The wording has also been reviewed in both French and English, and a number of outdated links have been fixed along the way. The application also moves to a new address: https://exp.mycentreon.com. The former address https://app.quanta.io keeps working and will be redirected later, on a date announced in advance. Your access, your data and your configurations are unchanged.Two points for administrators: point your API scripts to the new address right away, as cURL and other clients do not follow redirects by default, and add exp.mycentreon.com to your allowed domains if your network filters them.Full details in the release note are available here.Let us know what you think of the new interface in the comments.  

Hi everybody,My infrastructure is Central and poller is AlmaLinux 9.8 with Centreon 24.10.31.I made a lots of tests with CMA for Windows and I have a lot of questions : I tried CMA for Windows with Agent Initiated and for me there is a bug when I stop the CMA Agent to the host, because not warning and alert when agent not responding anymore. So I set freshness parameter to the service and that not working, when I set to engine, it’s working on duration (total time) and not on the last check and that my services became unknown every time that the time setting on the fresnness Parameter. that isn’t perfect for production environment.After that I tried with poller initiated the connection to the host, and there a lot of problem when CA installed to the infrastructure. but I found a solution for working this way with (need to creat a private key and generated the public certificat by the CA. did you try with CA Windows Corporate solution ?but some problems that i met, first : when the poll

Please note that the only procedures supported and maintained by Centreon are those published in the official documentation. If you have a question about this article, post it in the comments.Use this procedure if you are running Centreon 24.04, 24.10 or 25.10 on Debian 12 and you wish to upgrade to Centreon 26.10 (only Debian 13 is supported for this version).Run every command as root. Read each comment in the code blocks before running commands. Step 1: Before you start1.1 Take a snapshot of each serverSnapshot every server (central server, database server, MAP server, MBI server). If you have a remote database, take both snapshots at the same time, with Centreon stopped if possible. It is the only way to roll back quickly.1.2 Create dumpsSnapshots let you roll back a whole server quickly, but they do not replace backups. They usually share the VM's storage, capture databases only in a crash-consistent state, and cannot restore a single database or file. Once your snapshots are done,

Hello,we need to upgrade an existing Centreon poller from Centreon 23.10 to Centreon 24.04 in order to align it with our Central server, which is currently running Centreon 24.04.The poller is running Debian 11 (Bullseye).The repository previously used for Centreon 24.04 was:https://packages.centreon.com/apt-standard-24.04-stable/However, the Bullseye distribution is no longer available.The Bookworm distribution is still reachable:https://packages.centreon.com/apt-standard-24.04-stable/dists/bookworm/but its package indexes are currently empty.For example, the current InRelease reports:main/binary-amd64/Packages: 0 bytesmain/binary-all/Packages: 0 bytesAs a result, APT cannot retrieve any Centreon 24.04 standard packages.We have another working Centreon 24.04 server running Debian 12, which was upgraded while these packages were still available.It currently has, among others:centreon-engine   24.04.19-1+deb12u1centreon-broker   24.04.19-1+deb12u1centreon-gorgone  24.04.14-1+deb12u1cent

Dear Customer, Dear UsersThe PHP project has released security updates addressing two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, which may allow unauthenticated remote code execution.Centreon Cloud customers Following the announcement, Centreon immediately applied the temporary mitigations recommended by PHP. These changes were deployed without any observed impact on the service.Once the corrected packages became available, they were tested and validated before being deployed across all Centreon Cloud environments.All Centreon Cloud environments are now up to date and protected. No action is required from Centreon Cloud customers. Centreon On-Premise customers - action required PHP is not supplied, packaged or maintained by Centreon. It is installed through the packages provided by your Linux distribution or the community repository used by your organisation.For on-premise installations, the administration and maintenance of the operating system and its dependencies

Bonjour,Je voudrais savoir s’il existe un script d’installation silencieuse pour l’agent CMA sur Windows Server (2019 par exemple)Contexte : - Environnement : Cluster HyperV 2019- Environ 60 machines virtuelles et à 95 % sous Windows Server 2019 (le restant est soit du Linux soit de plus ancien OS Windows)- Quelques QNAP - Mon serveur Centreon est sous Debian 12 - Centreon version 25.10.1- Licence IT 100 activé- Centreon et l’agent Windows (Connexion TLS ‘Agent vers Server’ OK, Certifs générés depuis la VM OK ) semblent fonctionner à 99,99% (un faux négatif sur un disque QNAP, je chercherais pourquoi plus tard )- infos en option : gestion d’un parc informatique d’environ 250 PCs sur 20 sites distants → objectif : Superviser l’ensemble de nos serveurs et j’ai la flemme d’installer / configurer l’agent autant de fois 😂  Dans l’idée, exécuter le script d’installation silencieuse avec ou non les différentes options d’installation telle que le token, l’emplacement du log_file et log_level,

Hi,All is in the title.

Hi,Since the last update (version 20.10.4), I’ve been experiencing issues with my VMware setup. The account field in /etc/centreon/centreon_vmware.json is empty, and when I try to resend the login from the Centreon UI in the "Additional Connector Configurations" section, I get the following error:[parameters.vcenters[0].username] The string is empty, but a non-empty string was expected.This issue occurs on all my vCenter hosts. Do you have a solution? When I recreate a vCenter, it works fine. 

Bonjour,Mon infra Centreon est actuellement en 24.10 avec des serveurs Debian 12. Le but serait de passer en 26.10 avec Debian 13. Mais, sur la documentation officielle, je comprends que 26.10 ne supporte pas Debian 13 et je dois faire une migration. (Matrice des montées de version possibles | Centreon Documentation)Mais sur la même page, je vois que c’est compatible : De plus, sur Watch, je découvre une procédure pour faire exactement ce que je souhaite : Migrating from Debian 12 to Debian 13 on the same server, while upgrading Centreon to version 26.10 | CommunityJe souhaite donc savoir si la 26.10 est clairement et officiellement supportée sur Debian 13 ?Merci d’avance !

Please note that the only procedures supported and maintained by Centreon are those published in the official documentation. If you have a question about this article, post it in the comments.Centreon Infra Monitoring now offers a Matrix42 connector for Centreon Open Tickets, allowing your operators to open Matrix42 incidents directly from the monitoring console. This article provides a detailed guide to the complete configuration process from creating an API token to tracking the ticket within Matrix42. Centreon Open Tickets in a nutshell Centreon Open Tickets is an ITSM integration module. It turns one or more monitoring alerts into a ticket in your IT service management tool, with no copy-pasting between two interfaces.In practice, it lets you:Open a ticket in one click on a host or service in alert, prefilled with the host, service, state, duration and check output. Automatically acknowledge the resource when the ticket is created. Keep the alert ↔ ticket link: the ticket ID is sto

Bonjour,En suivant la procédure d’upgrade 25.10 > 26.10, il est évoqué pour les pollers, de récupérer la clé de déchiffrement en fin de documentation.Mes pollers sont “direct related” au Central.Lorsque je lance la commande avec les creds “admin”, j’ai une erreur “Authentication failed” alors que ces derniers sont fonctionnels en mode web. (et le firewalling poller > central est bien open sur TCP/443)Soit je n’utilise pas les bons “creds admin”, soit il y a une subtilité que je n’ai pas comprise / option non cochée dans le user “admin” ?Je suppose que c’est une nouvelle feature de sécurité liée à la 26.10 (chiffrement des échanges Poller <> Central ?) car je n’ai jamais fais cette action depuis que je m’occupe des upgrades de notre instance (version 21.04) Quelqu’un saurait-il me guider ? Par avance, merci !