Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GUI for configuration of default choices for command forms #3477

Open
spetersson opened this issue Jun 18, 2018 · 6 comments
Open

GUI for configuration of default choices for command forms #3477

spetersson opened this issue Jun 18, 2018 · 6 comments
Labels
area/configuration Affects the configuration area/monitoring Affects the monitoring module enhancement New feature or improvement

Comments

@spetersson
Copy link

Introduction

This is a feature request to this awesome monitoring community!

Is it possible to provide some kind of configuration page of default options in Icingaweb2?

An example:

When doing an acknowledge, standard choice is: "Send Notification". In our NOC their typical use case is to disable that and enable "Persistent Comment" and "Sticky Acknowledgement". We would like a configuration option where you could change these kind of default values in Icinga.
image

Solution

Provide a configuration page in the monitoring module where we could choose default values for every option in Icingaweb2, it would make it easy for all users to choose there default settings. Icingaweb2 could still be shipped with the current default options.

@cflinspach
Copy link

cflinspach commented Jun 19, 2018

It's not a GUI configuration page but you can find the default options in the monitoring module directory, in our cases it's /usr/share/icingaweb2/modules/monitoring/application/forms/Command/Object/AcknowledgeProblemCommandForm.php

We disable "Send Notifications" as default as well by changing the true in line 133 ('value' => (bool) $config->get('settings', 'acknowledge_notify', true), to false. The other options are in that file as well.

@spetersson
Copy link
Author

@cflinspach yes, tho that is probably not the ideal way to change the source code "settings". When doing package upgrades, this will be an issue that either is overwritten or there is going to be a .save file next to AcknowledgeProblemCommandForm.php where the updated code is.

@marcelfischer I'll test this! That is a suitable workaround, but I still think that we should have a Configuration GUI for this kinds of settings. Preferably store the settings in a MySQL database, so that Icingaweb2 could be put under a load balancer etc..

Thanks both!

@lippserd lippserd changed the title Configuration of default choices in Icingaweb2 GUI for configuration of default choices for command forms Nov 19, 2018
@lippserd
Copy link
Member

Hi,

Thanks for the report. We consider this for one of our next feature releases.

Best,
Eric

@lippserd lippserd added the enhancement New feature or improvement label Nov 19, 2018
@spetersson
Copy link
Author

@lippserd Thank you! Keep us posted regarding your consideration :)

As I mentioned above this would be great if the settings where to be stored in MySQL instead of a random file on disk.. Makes it's easier to loadbalance Icingaweb2 for future use cases.

@nilmerg
Copy link
Member

nilmerg commented May 2, 2019

This might be a candidate for v2.8. As already mentioned this is mostly of interest once we store such configuration in database. (#3770)

In the meantime, the available settings are now documented: https://icinga.com/docs/icingaweb2/latest/modules/monitoring/doc/03-Configuration/#default-settings

@nilmerg nilmerg added area/configuration Affects the configuration area/monitoring Affects the monitoring module labels May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/configuration Affects the configuration area/monitoring Affects the monitoring module enhancement New feature or improvement
Projects
None yet
Development

No branches or pull requests

5 participants