Centreon Infra Monitoring

Bonjour,J’ai une question par rapport à l’Activité métiers (Business Activity). Récemment, on m’a demandé de créer des activités métiers pour mes serveurs, mes applications hébergées. Cependant, je l’ai créé que depuis la semaine dernière. Cependant, les applications et les serveurs existaient depuis pas mal d’année. Par contre, quand je génère un rapport pour mon activité métier, il n’affiche que les valeurs à partir de la création de l’activité métier pour mes serveurs et mes applications. Est-ce normal? Comment je peux faire pour que ce rapport prend toute l’historique de mes serveurs et de mes applications? Ou ce n’est pas du tout possible?Aussi, j’avais déjà quelques activités métiers en place depuis pas mal d’année. Et j’ai modifié les plages d’horaire de rapport de 24x7 en heures ouvrées de 8h à 20h et aussi supprimer quelques indicateurs non utiles à mes rapports. Est-ce que j’aurai une réécriture de mes historique d’activités métiers dans ce cas là, ou bien c’

since middle on weekend all service usinf esx8 api popup same error:UNKNOWN: no data for resource host-709473 counter mem.capacity.usable.HOST at the moment. - no data for resource host-709473 counter mem.consumed.vms.HOST at the moment. - get_esx_stats function failed to retrieve statsThe counter mem.capacity.usable.HOST was not recorded for resource host-709473 before. It will now (creating acq_spec).The counter mem.consumed.vms.HOST was not recorded for resource host-709473 before. It will now (creating acq_spec). in debug on poller:== Info: We are completely uploaded and fine=> Recv header: HTTP/2 500=> Recv header: date: Mon, 09 Mar 2026 14:24:12 GMT=> Recv header: content-type: application/json=> Recv header: x-envoy-upstream-service-time: 13=> Recv header: vary: Accept-Encoding=> Recv header:=> Recv data: {"messages":[{"args":[],"defaul

Hello, just here to share to the community an issue that i encountered, the underlying issue, and how it can be resovled.This happened on a quite heavily loaded central server (poller included), and my end users reported receiving load of emails alerts regularly, but during bursts of a few minutes.After investigating the commands failing, there was nothing to correleate them, any service could fail, and all failed with the same output: “Execute command failed”. Something strange was at work here.After going more in the logs, especially centreon-engine logs, i find it. “Too many open files”. Here is the issue.At first i supposed there was permissions issues or something, but this is irrelevent as all can happend to any commands usually working fine. So i dig deeper on the internet, and here i find it, the Linux File Des

Hello,I’m facing an issue with discovery jobs stuck in Running state on my Centreon platform.Context Multiple discovery jobs configured per poller Providers used: VMware (ESXi & VM discovery, ~20 jobs with filters) AWX (2 jobs: pre-prod and prod) Pollers are sized according to Centreon recommendations Jobs are scheduled sequentially with intervals, running once per day IssueRecently, some discovery jobs are getting stuck in Running state indefinitely. On the central server, I get errors indicating that the job cannot be launched because it is already in Running state It is impossible to restart the job from the UI (even after waiting a long time and after restarting gorgoned service ) Checks already performed Reviewed gorg

Following a recent update of the plugins on my Centreon servers, I am facing issues with the Fortinet plugin, specifically impacting the SD-WAN and VPN services. Could you please assist me in resolving this issue? Unknown option: include-vdomain at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 4524.  Unknown option: include-vdom at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 4524.

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’

Hello everyone, I have update my centreon of the version 23 to 24.Since, i have this error "SSL certificate problem: unable to get local issuer certificate for" this error appears when I want to add a hostdo you know this problem? How to fix it?

Hello,I have a strange behaviour in my centreon (Centreon Engine 24.10.17).I´ve configured a passive check, set active checks enabled to no, passive checks enabled to yes, is volatile to no. Also check freshness to no: Now my Application sends an alert via centreon API and the service goes to warning state as expected.As soon as I acknowledge the service the active check command (which is a dummy command) gets executed and the service is in unknown state and therfore not acknowledged. Sticky acknoledge works but is unfortunately no option.So first question: Why is the check command executed on acknowledgement and second: how can I disable that?Thank

Hi!I’m trying to follow the tutorialto implement monitoring of SAP SCC. Two issues:HTTP basic authentication: it’s not clear from the tutorial how to get a plain simple HTTP basic auth. Took me hour to figure out (use the source, Luke!) that you just need to pass ‘basic’ like this: "authorization": {"basic": 1,"username": "%(constants.username)","password": "%(constants.password)"}, I would add it to the original post, but the comments are locked. Please add it, so people save a lot of time. Path depth. SAP will respond with a JSON of this type: {

Hello,I am facing an issue on a fresh installation of Centreon 25.10 running on Red Hat Enterprise Linux 9.7.Context Centreon installation: fresh install / from scratch OS: RHEL 9.7 Connector in use: Windows NSClient05 RestAPI License: IT-100 Plugin Pack installed online from the web interface Goal: use Windows disk discovery Issue observedWhen I open the discovery rule:OS-Windows-NSClient05-Restapi-Disk-NameI get the following error in the Centreon web interface:Command execution issue: status code '127'(command: /usr/lib/centreon/plugins//centreon_windows_local.pl --plugin=os::windows::local::plugin --mode=list-storages --hostname=127.0.0.1 --disco-format)

SymptomsWhen a host is linked to a host category, the update fails with the following error in the logs:  [ERROR] Rollback of 'PartialUpdateHost' transaction {"custom":{"trace":"#0 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHostValidation.php(258): Core\\Host\\Application\\Exception\\HostException::idsDoNotExist()\n#1 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(438): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHostValidation->assertAreValidCategories()\n#2 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(183): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHost->updateHostCategories()\n#3 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(152): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHost->up

Hi,I encounter this strange behavior for both AIX 6 and AIX 7, for all the hosts I tested: [centreon-engine@poller ~]$ /usr/lib/centreon/plugins//centreon_aix_snmp.pl --plugin=os::aix::snmp::plugin --mode=time --hostname=aixserver --snmp-version='2c' --snmp-community='xxx' --warning-offset='-5:5' --critical-offset='-10:10' --debugCRITICAL: Time offset 3600 second(s): Local Time : 2024-11-22T13:14:29 (UTC) | 'offset'=3600s;-5:5;-10:10;;.1.3.6.1.2.1.25.1.2.0 = ▒[centreon-engine@poller ~]$ snmpget -cxxx -v2c aixserver .1.3.6.1.2.1.25.1.2.0 HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2024-11-22,13:14:51.0[centreon-engine@poller ~]$ /usr/lib/centreon/plugins//centreon_aix_snmp.pl --plugin=os::aix::snmp::plugin --mode=time --hostname=aixserver --snmp-version='2c' --snmp-community='xxx' --warning-offset='-5:5' --critical-offset='-10:10' --debug |