Build better products with our product team.
Hi,At present time, anomaly detection doesn’t seem to take daylight saving time into account. The consequence is a time lag between the calculated envelope and the actual metric.Here’s an example for the past few days :time changing occured the 03/31 at 2PM day “1” is bank holiday day “2” : first working day since time changing, lag between metric and envelope, and therefore alerts are raised day “3” : just the same→ it would be nice to add this parameter in the calculations 🙂Thank you.
Some companies have a specific branding style and want to apply it to their application. Persona: this is mainly for sysadmins Problem to solve: personalize Centreon login page Expected outcome: a login page with desired background and logo Potential solutions: the possibility to load logo and background pictures Based on Github proposition
Hello all,We’d like to add downtimes period to “BA-Availability” reporting. In the same way the exception list appear :It would be easier for the people who receive the reports but do not have direct access to Centreon.Thanks you !
Bonjour, Avoir une zone de texte libre serait judicieux. Je dois noter des informations particulieres pour certains hôtes que j’aimerai voir apparaitre dans les colonnes du Dashboard. Par exemple annoter le numéro de contrat de nos prestataires télécoms ainsi que le numéro à appeler en cas d’incidents techniques. Ceci étant un exemple parmi d’autres.MerciCordialement Christophe BARAIREConseil Départemental de Tarn et Garonne
Hello.Please add a new plug-in for monitoring the state of the environment from a sensor in the UPS network management controller "PSU Sputnik".Suggested plugin name:hardware::sensors::inmatics::psusputnik::snmp::pluginSuggested plugin mode:environmentTemperature in Celsius (in this example, the value = 20.06 C):upsEnvSensorTemperature.1 = .1.3.6.1.4.1.54661.1.1.1.2.2.1.2.1 = INTEGER: 2006Humidity percentage (in this example, the value = 33 %):upsEnvSensorHumidity.1 = .1.3.6.1.4.1.54661.1.1.1.2.2.1.3.1 = INTEGER: 33Attached snmpwalk and MIB files: UPS-NMC-PSU-Sputnik.zip
Is it possible to add the downtimes information in the reporting of a BA?For a classic host, we already have it:But not for a BA:
The command-line API command to add a real downtime has a bug imho.To make it work you must use the exact name (it is case-sensitive) of a host object. If you use a name which doesn't match the exact host object name it will not show you any error but a downtime will not be created.centreon -u admin -p 'centreon' -o RTDOWNTIME -a add -v "HOST;central;2017/09/24 10:00;2017/09/24 12:00;1;3600;my comments;1"I didn’t observe it using other CLAPI commands. This should be fixed I think. Best regards,Jaroslaw Kesy
Hello, Have you ever considered changing the naming convention for the term “services”?The term “service” in Centreon actually means a “check” or a “test”. Many times, when training our users how to use Centreon, we had to explain that “services” in Centreon should not be confused with services in Windows or some other activities/services that involve “doing things” for customers or other systems and that they should think of them as tests or checks.Best regards,Jaroslaw Kesy
Hello, problem: BI ETL rebuild is quite difficult to use. Not user friendly at all and doesn’t meet the standard level of quality that we should aim at. documentation is fine but difficult to understand because the ETL concepts are not monitoring concepts and people are not familiar with that script usage is prone to error (not running it in nohup and losing ssh connexion, running them with wrong arguments...)solution: do better! (easy isn’t it?) We now have all the technologies to build a good UX.Put gorgone on the BI server, create a gorgone module called “centreon-bi-etl” since gorgone and etl are all Perl, it can just call the ETL. (could be a good opportunity to refine the ETL. There may have some optimisations to do) Gorgone on the central server is going to send orders to gorgone on the BI server. Since it can only work using async communication, gorgone on the BI server must send errors, logs and end of execution to gorgone on the central server Do a well crafted web interface that will help people build the ETL orders that gorgone must send. It must work in a full async mode, gorgone on the central server must be able to communicate all information to the web interface hours after the user has made the action.Features: This is not a comprehensive listweb interface must parse results of centreonBIMonitoring --db-content script and compute them to preconfigure the action that the user will have to do. For example [Table mod_bi_hostavailability, last entry: 2020-07-01 00:00:00] means that the web interface needs to guide the user through a host data import, host event rebuild without purge since 2020-07-01 (that means no data bin import, when using importdata.pl, and then use the build dimension script and then the build event script and not the perfdata one) web interface must have an easy wizard that clearly displays what are the consequences of the actions. For example, the web interface ask you do you want to rebuild or apply a new configuration to old data ? (we can even explain what’s the meaning of applying a new configuration to old data) what kind of data do you want to work on ? events, perfdata, both ? (we can even explain what’s the purpose of those types of rebuild rebuild starting date is and end date is ? Since start and end date are confusing (we never now if the date is included or excluded) we can compute on the fly the meaning of that. For exemple start date = 2022-03-10 means that it will include datas from 2022-03-10 00:00:00 and end date = 2022-03-22 means that it will include datas until 2022-03-22 00:00:00 do you want to purge data that are outside of the selected time range ? (no should be ticked by default) verbosity of the action ? (error, debug...) before running this it should : display an overview of what you’ve configured. You should have a clear warning message if purge is ticked to yes before running you should have the list of commands that gorgone will run in case you would like to do that manually (could be very useful when trying to rebuild huge amount of data when a rebuild is ran through the web interface, the bi-engine cron must be disabled. It must be enabled back when the rebuild is done and a centreonBIMonitoring --db-content must be run automatically. And if things are not up to date, the web interface should compute things for the user as stated in the first bullet point If a rebuild fails, the logs must be available through the web interface (see the solution part of this topic). There are numerous reason why it could fail and it can be quite tricky to solve this. In order to help people, it should display the link to the Centreon support website and it must have a button that will copy in the clipboard all the required information for the support. This means: centreon versions (web + gorgone + bi) the configuration made by the user using the wizard the commands that gorgone must run according to this configuration the logs of the operation the result of a the biMonitoring --db-content command it must have a “task history” menu. Meaning that a rebuild run by gorgone should have a kind of task id. When clicking on an already finished task you should be able to see: centreon versions (web + gorgone + bi) the configuration made by the user using the wizard the commands that gorgone must run according to this configuration the logs of the operation the result of a the biMonitoring --db-content command ----------------------------------------------------I think that’s all the ideas I have at the moment. Maybe I’ll do a mockup/POC on my free time for the sake of fun and learn more about gorgone.
Hello,We find working with standard pagination controls in Centreon Web (in different pages) extremely unconvienient. The controls are small, very close to each other that it takes sometimes too long to “point” the right control or clicking a wrong button.They look and feel a little bit better in Custom Views but still too small IMHO. I would recommend to redesign them so it would be more comfortable using them. With CSS it should be a “low-hanging fruit” goal. The pagination controls introduced in BAM configuration pages (not in all pages in BAM) look and feel much better and are better placed (right-aligned) although they are missing controls with the numbers of pages.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.