Skip to main content

    Filter by idea status

    Filter by product

    301 Ideas

    Cm123Builder **

    Create simple Availability graph for number of host and services and there status.Needs Votes

    Hello, I suggest creating a new dashboard or enhancing the existing one (Availability)within Centreon to provide a comprehensive view of the total number of services and hosts, along with their status. This dashboard should prominently display information such as number of OK, Critical, Warning, Unknown, and Pending services/host statuses in real time.Key Features of the Dashboard:Live Status Updates: Display the total number of services and hosts  and status in real time, allowing us to quickly identify any issues or anomalies. Different Time Frames: Provide options to view status trends over different time frames (e.g., daily, weekly, monthly) for historical analysis and trend identification. User-Friendly Interface: Design the dashboard with a focus on user experience, ensuring that information is presented clearly and intuitively. Impactful Visualizations: Utilize visual elements such as charts, graphs, and color-coded indicators to make the dashboard visually engaging and easy to interpret.Benefits:Improved Monitoring Efficiency: The dashboard will enable us to monitor a large volume of data more efficiently, reducing manual effort and streamlining decision-making. Real-Time Insights: With live status updates, we can promptly address issues and maintain optimal performance across our infrastructure. Historical Analysis: The ability to view status trends over time will facilitate trend analysis, proactive maintenance, and performance optimization.I believe that implementing this enhanced monitoring dashboard will significantly enhance our monitoring capabilities and contribute to a more proactive and efficient IT environment.Thank youcm123

    jstagerBuilder *

    Auto Discovery - regular automatic execution/schedule for servicesNeeds Votes

    Hello all,As it is already possible to automate and schedule the automatic discovery of new hosts.We want to be able to do the same with automatic service discovery.Indeed, this automation process has already existed for a few years for the hosts discovery but will be much more useful for the services configurations.A host's services are added and removed much more regularly than a host itself.This is not convenient that auto discovery for services remains manual and cannot be automatically scheduled. Indeed, we have autodiscovery templates for services but these must be activated manually each time an network interface is added on a host.It would also be very convenient if the services corresponding to the interfaces could be activated and deactivated depending on whether the interface is admin-up or admin-down.Today in the state of this manually-autodiscovery-service-process as soon as a virtual or physical interface is added we are forced to run several different templates for a single host. It will be nice to don’t have to worry about this and don’t wast time for that.Indeed today we scan (manually) and add and active all the serivices-checks for all the interfaces of a host whether they are admin-up or admin-down in order to avoid executing the manual-autodiscovery with many templates on many hosts every 2 days. It would be great if these jobs ran automatically at scheduled intervals. Thanks a lot

    cgagnaireSteward *

    Handle metrics instances in graphs legendNeeds Votes

    Hi,Since the new Centreon Plugins metrics system, information about “instances” (or one can call it dimensions) are splitted front-side to only show the metric name in the graph’s legend.That is fine. But we loose key information.Here is a common example with a check on the Poller delays.At first glance, we have the same metric eight times: But if we put the mouse over one metric we’ll see a tooltip showing the exact metric name, with the “instance” part, here “Central”: My proposition is to show that splitted-out part in the legend, for example as a label (i am no front dev!): This will show the information without overing on the legend, but it is also “needed” to benefit from the data sources definitions (you know, the underused ‘Monitoring > Performances > Curves’ page).Because as of know, the curves will not use the templates if doesn’t match exactly the data source (read metric) name, which is totally fine too.Splitting the metric not only front-side but back-side can leverage the use of those templates, which can result to having both templates (legend, color, etc) and instances on graphs.An example here on Broker statistics check, with 3 different metrics for 1 instance with curves templates for each metric: Of course there are several scenarios.Here an example with the same metric on multiple instances :This one is tricky as the curves should not have the same color.There is also the “2 dimensions” metrics case with metrics built like “dimension1~dimension2#metric”.Let the discussion begin!