Hello,If we referred on ITIL, the problem term means the cause of one or multiple incident recursive or not.It could be known (if we haven't yet found a solution) or not if it's new.Generally, the IT monitoring give events who are not yet qualified of an incident and no more problems.It should be good to have global ITIL approach around centreon ( Web UI, Training, etc...)For example, in the training sessions we talk about problems, incidents and events here or there. All of this always referring to alerts raised by Centreon. This can lead to confusion.During the presentation of Resource Status, we talk about “event tray”, it seems to be the good language.In fact, problem term is principally present in dropdown list filter on “Resource status” and legacy pages “Service Monitoring”. Persona: All users of Centreon and all IT services who work around Centreon with ITSM or CMDB softwares (and so much)Problem to solve: have a common language all time of usage of centreon since training to production usageExpected outcome: a better experience around CentreonPotential solutions: Replace the term "problem" (and, if applicable, "incident") by event term on the web interface (and on trainings and docs as far as possible).See below for example where we can find problem term:
Hi, i’m trying to update centreon to the latest vesion 22.10 on a rocky9.I’m blocked because centreon repo doesn’t provide php-pecl-gnupg >= 1.5.Official Remi repo name this package php81-php-pecl-gnupg.Is it either possible to add the version 1.5 of php-pecl-gnupg on centreon repo or to add php81-php-pecl-gnupg to the dependencies list of centreon ?
An host/service context menu in MAP to manage downtimes when working with a map. Centreon operator. When interacting with host and service objects on a map in MAP module an admin or a user (with proper ACLs) can right-click an object and a context menu is displayed with the options related to downtimes: - Add downtime - Delete downtime - Delete current downtime A user can add a downtime quickly from here. But a user cannot “Delete downtime” or “Delete current downtime”. To do that a user must go to Monitoring > Downtimes to cancel upcoming or current running downtime. It is very inconvenient for our users. They see a menu option and they expect it to be working as expected. I created a ticket for it as for me it looks like a bug but I was informed this functionality was deprecated(!). Please, make these options “Delete downtime” and “Delete current downtime” to work as expected from the context menu available in MAP.
hellosome colleagues have a server or NAS at home which is running uptime-kuma, and they have created a status page for DHL public internet services. These uptime kuma instances run locally, so we created a page to test from the source of every ISP in our part of the country…(from the principle: page of colleague A going down → ISP issue vs all pages showing issues → effective problem with our public services)I would like to display such a service overview within Centreon, but we are receiving a connection refused error…Other (PHP/HTML based) websites are displayed correctly, but when I curl the UptimeKuma status page, no webpage body is displayed...I guess because the node.js parts are not renderedI could easily build a similar view in Wordpress, but the monitoring plugins in wordpress are running somewhere on a cloud subscription (and not locally) and this is a disadvantage: I do not want to provide a list of my company hosts to a third-party, and the monitoring then relies on the uptime of a single cloud subscription which is basically blackboxThis HTTP loader would allow the addition of http(S) monitoring from public webservices, from the public perspective of various local ISPs, displaying it internally on the central monitoring solution
It’s very difficult in the web console to search for the opposite of items e.g. I need to know how many hosts are not in hostgroup i.e. they have not been assigned to any groups. As we use these groups to assign ACLs it’s important that they can be picked up so having the option to choose all the hostgroups and then a “not” would allow this.
Additional filter in "Configuration > Pollers" page Centreon administrator/operator. When there are a lot of remote pollers confgured (we have moire than 40) and the configuration for lot of them changed it is very unconvienient to click checkboxes at each one for which Conf changed (let say for 10 out of 40). A checkbox is added in the filter area to display only pollers marked with "Conf Changed" flag. So one can quickly select this checkbox so only the ones for which “Conf changed” are displayed. One can use “Select all” checkbox with one click and export the configuration without clicking one by one going through a long list.
Marking correctly pollers for which "Conf Changed" when a host is moved from one poller to another.. Centreon administrator/operator. Our observations are that when a host object is switched from one monitoring poller to another one only the other poller is marked as "Conf Changed". And when only we send the new configuration to this marked poller then the previous poller doesn't know that a host object is moved to another poller. The previous poller keeps running checks for the host object until it is is reloaded by some other change in config which affects it. Both pollers are marked with "Conf Changed" flag.
A user/contact with RestAPI access to submit results for passive checks. Centreon administrator/operator. We are using passive checks for which results are sent to Centreon over RestAPI v2. A custom script which communicates with Centreon over RestAPI is using a user account which must have admin rights and which must also be allowed reach Centreon Front-end. When you deselect “Reach Centreon Front-end” option the user will not be permitted to login via RestAPI. Our script is running on remote machines which don’t belong to us. It is not very secure to leave inside our custom script the username and password which can be used to access Centreon front-end. But at the moment we have no choice (I can encode the password while using Powershell for our script but any local admin with some system knowledge can decode it). At least in one of the previous version we could deselect “Reach Centreon Front-end” option but it stopped working. A user can be configured in a way it can submit check results for passive checks over RestAPI v2 but it doesn’t have to be an admin and can be configured to not be allowed to “Reach Centreon Front-end”. So the username and password can be stored in a script and it is uselesss when trying to connect with Centreon Web GUI. Such a user can be assigned a generated token only for RestAPI communication so the token can be stored within our custom script without revealing the password for the user. Also using ACLs such a user could be configured to be allowed to submit check results only for host objects it has access granted in Resource Access.
Persona: This is for an IT managerProblem to solve: no monitoring about Symantec Mail Security for Microsoft ExchangeExpected outcome: monitoring state of licences and definitions in Symantec Mail Security for Microsoft ExchangePotential solution: add a plugin pack for Symantec Mail Security for Microsoft Exchange
I ll try to explain myself :- ) when you pass over the menu with mouse , it open and stay for few second .When you work so fast as me ;-D , it s awfull when (by mystake ) you had to wait that this menu closed to acces the field below … Ca we have the choice with mouse gesture, maybe the possibility to open menu with a click ?
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.