search

Icinga / icingaweb2-module-director

The Director aims to be your new favourite Icinga config deployment tool. Director is designed for those who want to automate their configuration deployment and those who want to grant their “point & click” users easy access to the configuration.
https://icinga.com/docs/director/latest
GNU General Public License v2.0
413 stars 203 forks source link

[enhancement request] - to be able to comment the changes #2833

Closed btrnka63 closed 10 months ago

btrnka63 commented 1 year ago

Hello, I'd like to suggest/request to add new field "Comment" into each modification form to be able to enter a comment/reason why performing the change. This information should not be stored (optionally it could be) as part of the edited icinga object (host, service, ...), but stored only as part of the "Activity log" entry.

The intention is to be able to comment the activity to document the reason of change (e.g., to enter request ticket number, etc.) - it could help to remember why it was done latter when reviewing the history.

Thanks.

btrnka63 commented 1 year ago

Something like:

image

image

nilmerg commented 10 months ago

Hi Boris,

this is already possible by using Icinga Director Branches.

There are no plans to add this to Icinga Director.

Best, Johannes

btrnka63 commented 10 months ago

Hi, thanks for your comment. I will review the functionality of branches module, but let me ask: does it mean each time user changes single threshold (e.g., for CPU check from 90 to 95%) there will be / has to be a new branch?

nilmerg commented 10 months ago

There's a talk on YouTube showing the details, please take a look at that.

btrnka63 commented 10 months ago

will do, thanks