Skip to main content

    Filter by idea status

    Filter by product

    644 Ideas

    gespadaBuilder ***

    [UI] Drop-down list command event handlerIn Backlog

    Hello Watchers, Centreonians,As suggested by Centreon Support, i create an idea about the dropdown list for the event handler command.Documentation of Centreon indicate to use the Misc / Divers command type for the event handler.https://docs.centreon.com/docs/monitoring/event-handler/#configurationhttps://docs.centreon.com/fr/docs/monitoring/event-handler/#configurationBut when you select the drop-down list, you have all the type of command at the exception of the Discovery Command on BAM, Service config tab, host config tab or poller config tab who authorize the usage of an event handler command :https://docs.centreon.com/docs/monitoring/basic-objects/services/#data-processing-tabhttps://docs.centreon.com/fr/docs/monitoring/event-handler/#configurationhttps://docs.centreon.com/docs/monitoring/basic-objects/hosts/#data-processing-tabhttps://docs.centreon.com/fr/docs/monitoring/basic-objects/hosts/#onglet-traitement-des-donn%C3%A9esIt’s not logical to have all the command (Check, Notification, Event Handler), could you apply a filter to Misc command to be coherent with the Check Commands, the Notification Commands, the Discovery Commands Persona : As a Centreon Administrator, or an Operator with rights Problem to solve : It’s complicated to retrieve a misc command type on event handler with BAM module, engine configuration of a poller for a global event handler for service or host and also for the host or service configuration. Expected outcome : Simplification of the selection of an event handler command, win times, avoid mistakes, limit to the functionnality Potential solutions : I want a drop-down list for the event handler command who filter the Misc command with a filtering by words like for the check command  Regards,Greg

    GHT ArmorSteward *

    Besoin Plugin Seagate EXOSNeeds Votes

    Bonjour,Nous implémentons actuellement des baies de stockage Seagate EXOS X (6 unités)Ces baies sont notamment utilisées par Dell pour leur gamme Powervault, qui bénéficient d’un plugin Centreon en mode Rest API.Nous avons ainsi utilisé le plugin “storage::dell::me4::restapi::plugin”, cela fonctionne bien, mais nous rencontrons 2 “disfonctionnements”, potentiellement en lien avec des différences entre Dell et Seagate.Le premier souci a été rencontré lors du recettage. Si nous retirons un disque SSD, le mode “hardware” du plugin reste en vert car il ne monitore pas l’état des “pools” et des “disk-groups”. En effet, en retirant un SSD, le monitoring “disks” passe de “28/28 disks OK” à “27/27 disks OK”, il reste donc au vert. Pourtant l’interface restapi remonte bien le pool et le disk-group associés en “dégradé” en consultant sous “/api/show/pools” et “/api/show/disk-groups”. Le deuxième souci (moindre) concerne le monitoring des host-interfaces de la baie. Sans savoir si cela vient du software Seagate EXOS, ou de nos modèles de baies en Fiber-Channel, mais le web service “/api/show/host-phy-statistics” n’est pas disponible et renvoit une erreur 400 dans notre cas. Nous avons triché et modifier le “interfaces.pm” pour initialiser la variable “ my $result_logical_interfaces = {};’ à vide, et permettre un retour sur les autres informations, peut-être serait-il possible de faire un switch/filtre en fonction du hardware utilisé. Serait-il possible de faire évoluer le plugin Dell, ou de créer un plugin “storage::seagate::exos::restapi::plugin” plus adapté ? La différence semble minime si ce n’est la création des “Components” disk-group.pm et pool.pm.Merci de votre compréhension?Cordialement,le GHT Armor

    Centreon LTSReleased

    Hi,I’d already suggested this idea during the last Centreon summit but I’d like to know the point of view of the community.I think it would be great to have a LTS (Long Term Support) version of Centreon. Like the Ubuntu GNU/Linux distribution does, or some other softwares too. Not only OS or frameworks. There is a non exhaustive list here.A two year support may seem long enough for a software like Centreon, but in my opinion (and from experience) it’s not.Plus, for the support teams, it would probably be less different versions to support. For example, currently, with a two years support for every version, and a release every six month, there are always four versions supported anytime. But, if we keep the six month period release, and support only one year every version, but four years for a LTS version, which would be every five releases (21.10, 23.10, 25.10, …) it’s only three versions supported at the same time. This rythme is just an example, maybe there are better choices.Somebody once pointed to me that it may be hard to choose if a particular functionality should be included in the next release or if it’s better to wait to include it in the next LTS release. Or if a change should be applied to the LTS or not. In my opinion it’s not so hard: a functionality should be released when it’s ready, and the changes that should be made to a LTS are only bug fixes.As a last example: Zabbix, another monitoring software (also released under GPL except for the documentation), has a LTS period of five years.I did not make the effort to translate this post in French, but feel free to answer me in French if you like, French being my native language I’ll be happy to answer you in French.Best regards.

    FredericGerard
    FredericGerardSteward **

    Virtual Curves (Centreon SQL Metrics) : improve output messageNeeds Votes

    Hi,We’ve got a question/suggestion about the « formatting » node and outputs messages of virtual curves.Let’s say 2 virtual curves are defined for traffic network, summing incoming interfaces on one hand, outgoing on the other. Since the same printf_msg is used for each virtual curve, it has to be generic. So, just reading the « status information », one can’t figure out which one is the incoming traffic an which is the outgoing.Ex of current output:Status informationOK: Traffic on data interfaces is OKTraffic SUM is: 15.32 Mb/sTraffic SUM is: 7.82 Mb/sFiguring it out requires to get to the « performance data » and is neither explicit nor convenient.Persona : ITOps teamsProblem to solve : same output message for all the set of metrics of a virtual curves serviceExpected outcome : customize output of virtual curves servicesPotential solution :Offer possibility to define a « comment » entry in the virtual curves definition section with free entry.Ex :"virtualcurve": {        "sum_traffic_in": {            "pattern": "^traffic_in$",            "aggregation":"sum",            "comment":"IN"        },        "sum_traffic_out": {            "pattern": "^traffic_out$",            "aggregation":"sum",            "comment":"OUT"        }    }Then formatting node could be :"formatting": {        "change_bytes_network": 1,        "custom_message_global": "Traffic on data interfaces is OK",        "printf_msg": "Traffic %s SUM is: %s %s/s",        "printf_var": "$self->{result_values}->{comment},$self->{result_values}->{value}, $self->{result_values}->{unit}"    }And expected resultStatus informationOK: Traffic on data interfaces is OKTraffic IN SUM is: 15.32 Mb/sTraffic OUT SUM is: 7.82 Mb/sRegards