Persona: Centreon administrator Problem to solve: Some companies or associations do not have room to install a physical server or a virtual machine. The installation of a Raspberry Pi with a simple power outlet is possible. Expected outcome: monitor small infrastructures. Potential solutions: package Centreon Poller for Raspberry OS or provide OS image.
Names of services in Administration > Parameters > Data page for meta services display generic names (meta_1, meta_2, meta_3, etc), This makes it impossible to recognize which meta services they are related to.This is the type of information we would like you to describe: Persona: Centreon administrator Problem to solve: sometimes it is required to clear performance data for some services but with the current situation for meta services it is not possible to do it correctly as the identification of meta services is not possible at all. Expected outcome: names of services in Administration > Parameters > Data page are the names of related meta services like they are for regular services. Potential solutions: not aware of any possible right now
We want to provide the dashboard access to some of our customers.Though it would be read only access, we expect our customers to perform basic things like password reset.Is there a way Centreon has capability for the users to reset their passwords on their own? Even if it is via a password reset link?
Would it be possible to consider a monitoring connector for the Cohesity on-prem backup solution? I believe they have an API that can be exposed for monitoring.
I have raised this as a bug in the HTTP Loader and it was rejected there, yet, I have discussed this feature request with a Centreon support guys and he was keen on raising this again as a new feature, and not a bug.Allow me to explain why this feature would be absolutely great in Centreon...Many of my colleagues including myself 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)https://uptime.kuma.pet/The enormous advantage of this tool is that is is freeware, largely deployed, available on all OSes and IOT devices and is not hosted in the cloud, hence you can really do checks per ISP.I would like to display such a service overview (the “external” view into our applications) within Centreon, but we are receiving a connection refused error…Other (PHP/HTML based) websites are displayed in the HTTP Loader 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 blackboxIf Centreon could create something similar to the HTTP Loader, this 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
For security have the possibility to monitor MSSQL dbengine with Active Directory service account rather than a local MSSQL account.Plugins : /usr/lib/centreon/plugins//centreon_mssql.pl --plugin database::mssql::pluginRegards
Persona: Centreon administrator Problem to solve: Too many clicks to create a host, apply templates, go to the “Service Discovery > Scan menu”, discover all services with all discovery rules Expected outcome: Ease of use Gain of time Potential solutions: Allow to acces service discovery within the host configuration menu. It would display all the results of all the discovery rules applicable to the host, and the user would be able to select them and when the host is saved, everything is created. Then all that is left is exporting the configuration to apply it on the pollers.
It will be easier if all stream connectors were packaged.Acutally, we have to download/clone it from GitHub repository (https://github.com/centreon/centreon-stream-connector-scripts.git ) and move the script to the directory /usr/share/lua/5.3/centreon-stream-connectors-lib/
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.