Recently active topics

Same as this idea:This would be useful for building dynamic action_url links to automate remediation actions, or using notes_url to generate specific Wiki pages.

Hi,The centreon nrpe client is no longer OOB compatible because of the key (C:\Program Files\Centreon NSClient++\security\nrpe_dh_512.pem) which is only 512 instead of 2048 required.Currently, I have a server upgrade (centos7 to rhel8) and I have the following error: CHECK_NRPE: (ssl_err != 5) Error - Could not complete SSL handshake ….By replacing the 512 key with a 2048, it's ok.It would be nice if the Centeon nrpe client version could have a 2048 key from the installation in order to have an operational nrpe module from the installation.Best regards, 

Bonjour,  Nous avons un écran de supervision avec différentes “maps” dans la rubrique “Tableaux de Bord”, mais malheureusement, il n’y a pas de paramétrage précis sur le fait de retirer les services/hôtes du widget une fois l’acquittement effectué :  Cela pourrait permettre de gérer notre supervision en temps réel afin d’avoir pour objectif le retrait des hôtes/services une fois qu’ils ont été acquittés. Merci d’avance. Cordialement, Nelson - Support Exaprobe

Actually if we set a warning at 120 minutes from Windows CMA & centreon returm an alert if less 2 hour by default template, this is nice if the server just reboot without agree about IT support.it was nice if we can make the opposite too for example if above 1 month the host doesn’t restart for a long time … 😁 then Centreon send an alert iffrom nagios or snmp  we used this parameter below when we wanted to receive an alert before or after time second, minutes, hour or day ?@0:200  ~:200 200: :200 >200it was very interesting if you could add this function to Windows CMA

Hello, A nice feature would be to be able to use macros within custom macros.For example use $hostname$ in a URL like this in order to use the hostname do dynamically create the URL.Thanks in advance for the consideration.

Hello.Could it be possible to delete finished/cancelled downtime entries in the centreon_storage.downtimes table from the GUI? I don't mean cancelling a current downtime, I mean deleting the entry in the database.In the Monitoring -> Downtimes page you can list, filter and cancel a current downtime and show finished/cancelled ones. An option to delete entries filtered by End Time, Cancelled status Yes and/or Author would be nice.When displaying finished downtimes we have 116400 entries, the oldest from 2018. We would like to delete those older than 4 years or those from a specific author, for example. Regards

Le message de fermeture de ticket dans Open Ticket devrait dépendre du provider parce que dans mon cas, j’utilise Service Now et la fermeture des tickets n’est pas comprise dans les options et les superviseurs sont confus à chaque fois qu’ils voient ce message :  

Hello.We would like to use the Oracle Database connector but it has a perl library as a prerequisite, which has to be downloaded and installed manually from a 3d party source (not Centreon’s or OS repositories).For security reasons, we are not able to download/install anything that is not in our SUMA (SUSE Manager) channels. Our Central and pollers are registered to Oracle Linux channels and we have also Centreon's repos in our SUMA Service.So, would it be possible to add that package to Centreon's repositories? Meaning that it has been tested by Centreon so it is guaranteed to be a version compatible with the current connector and also secure for installation.The other dependency, the Oracle Instant Client is also available through official repos, so that is not a stopper for us.Regards

Idée de développement pour équipement Keysight.

Dear Centreon, The 1.5-year support period for STS versions is too short.These versions should be supported for two years. The Phase 2 support period for STS versions is too short.Support for STS versions ends before support for the previous LTS version, which makes no sense. Support for STS versions doesn't allow us to reach Phase 2 of the next version, which is problematic for achieving a minimum level of stability and security.  STS versions seem to be paid beta tests with the risk of being blocked by unsupported bugs. Whereas previously we benefited from two major versions per year, each supported for two years, today we only get one major version every two years. Please extend Phase 2 support for STS versions from six months to one year, so that they are supported for two years, allowing us to move to the beginning of Phase 2 of the next LTS version. Thank you in advance for taking this into account.

Hello.Would it be possible to have more information about the hosts/services involved in recurring downtimesFor example, a log of which hosts/services, and by who, were added to or removed from a recurring downtime.If that's too complicated, at least having a field called “Notes”, “Information”, “Comments”, or something similar where you can record the actions taken in each configured recurring downtime would be useful. Regards

Hi, I propose that Centreon can give the possibility to know who has delete downtime. Centreon can just know who has add downtime. Cordialy,Francis DOUNGA