Skip to main content

    Filter by idea status

    Filter by product

    629 Ideas

    Jaroslaw KesySteward **

    A user/contact with RestAPI access to submit results for passive checks (RestAPI v2).Needs Votes

    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.

    gespadaBuilder ***

    [PLUGIN PACKS] About the centreon-plugins of notificationDeclined

    Hello,To answer about the issue https://github.com/centreon/centreon-plugins/issues/3671 Many plugins exist to notify or open/close ticket :Ticketing :Centreon Open Tickets https://github.com/centreon/centreon-plugins/tree/master/notification/centreon/opentickets/apiSirportly tickets https://github.com/centreon/centreon-plugins/tree/master/notification/sirportlNotification : Foxbox Notifications https://github.com/centreon/centreon-plugins/tree/master/notification/foxbox HighSMS notifications https://github.com/centreon/centreon-plugins/tree/master/notification/highsms Jasmin SMS https://github.com/centreon/centreon-plugins/tree/master/notification/jasminsms/httpapi Microsoft 365 Teams notifications https://github.com/centreon/centreon-plugins/tree/master/notification/microsoft/office365/teams OVH SMS https://github.com/centreon/centreon-plugins/tree/master/notification/ovhsms iOS push notifications via Prowl https://github.com/centreon/centreon-plugins/tree/master/notification/prowl Slack/Mattermost notifications https://github.com/centreon/centreon-plugins/tree/master/notification/slack Telegram notifications https://github.com/centreon/centreon-plugins/tree/master/notification/telegramA tutorial exist for implement Teams notifications also :My idea about the centreon-plugins of notification, is to plugin packed them with a dedicated subsection.By this parameter, the plugin would be deployed on the poller (New feature of 22.04) and could be configure or preconfigure the notification command.In fact, the Notification Commands page is not really simple to understand, by default we have preconfigured command like :bam-notify-by-mail [host|service]-notify-by-mail [host|service]-notify-by-epager [host|service]-notify-by-jabberAll the notification command are just a printf command to embedded the result of printf command in a mail command, an epager command, except for Jabber where a NRPE command is defined.If you want an exemple to configure a notification command like the plugins, you don’t have that :pThe goal of this idea, is to facilitate the configuration of a notification command and maybe extend the possibility of notifications process of Centreon by the plugins more easily.As the Idea to refresh the UI of command and macro :The notification Command could be improved with a JS Library of Code Editor https://openbase.com/categories/js/best-javascript-html-editor-libraries Persona : As a Centreon administrator Problem to solve : Configure a notification command is not easy to understand with the existent (mail, epager, etc..) Many organization looking for to exit of mail notification for the alerting process.  Expected outcome : Use the Plugin Pack process to facilitate the process of configuration about the notification command and maybe more and extend the possibility of notification more easily. Potential solutions : Build a new subsection of plugin pack in order to configure or pre-configure the notification command. For the preconfigured command, you could indicate the command is partially configured (Please add server, port, protocol, etc.. and others) you could arbitrary preconfigure the centreon URL by replacing it with the centreon parameter,  Regards,Greg

    Force reinstall/deletion of a plugin packDeclined

    Hi,Currently it’s impossible to delete or reinstall a plugin pack if some templates depend on it. Clicking on the reinstall button silently fails, and clicking on the uninstall button shows this kind of message: A re-installation of the pack would be, according to the support (see #59974), the only way to recover a missing icon file, consequence of a Centreon data migration procedure. It could be useful too if someone wants to reset a *-custom template he had modified.Forcing the deletion of a pack should be possible, as it’s possible to have a template without a parent template (even if it leads to a broken engine configuration).The idea is the following: permit to force the deletion of a pack even in case of template dependencies.Remark 1: The migration procedure I linked is the one for the 21.10 version because I can’t find the corresponding one for 22.04 or 22.10. I think the migration is still possible with those versions, because the migration from version 3.4 still exists for 22.04 and 22.10. So the procedure should still be in the documentation for those versions too.Remark 2: There is another obvious workaround to recover the missing icon file, that’s to copy the file from another Centreon platform. But it’s not acceptable having to install another platform (if one doesn’t have one already) just to recover a missing PNG file. Moreover, I’m not sure of the relevance to depends on the installation step in the Centreon GUI, rather than having the PNG file directly installed by the RPM package. It would be far more easier to manage from an user point of view.