Remove Autodiscovery Feature

[emartine]

Perfect. Yes an upgrade will override this. I removed the autodiscovery wizard but the link remained with a message:

Installation Problem
An installation errror was detected. The following steps must be completed before using this component:
Run the setup script. To do this, login to the Nagios XI server as the root user and issue the following commands:
chmod +x /usr/local/nagiosxi/html/includes/components/autodiscovery/setup.sh
/usr/local/nagiosxi/html/includes/components/autodiscovery/setup.sh

A feature request to remove this link would be great. Toggle function?

[tmcdonald]

A feature request can be put in, though this is kinda specific.

I did the following and it seemed to work:

Code: Select all

mv /usr/local/nagiosxi/html/includes/components/autodiscovery/ /tmp/autodiscovery_comp
mv /usr/local/nagiosxi/html/includes/configwizards/autodiscovery/ /tmp/autodiscovery_wiz

So you can probably also remove it.

Pretty sure upgrades don't also re-install components or wizards, only a full install will.

[emartine]

I'm kinda weary about removing components by moving them out like that since I did that for some of the monitoring wizards.. forgot about them... did an upgrade and I got errors from the update. It didn't tell me it was successful... but reviewing it, all of the components except for the wizards updated successfully. When a newer update came out I moved the wizards back and then did the upgrade which worked without issue.

[jdalrymple]

emartine,

I got to thinking about your feature request - how would you like to see the toggle implemented? The problem I see is that admins are admins... and if you have a toggle that turns off auto-discover who's to say an admin won't just go in and turn it on again? Would it be something that you might like to be seen toggled in a more complicated (config file) sort of fashion to discourage people from using it, or will you have the need for another layer of administrator put in place? The latter is certainly a bigger change to the product, but the former isn't much more than what I offered regarding commenting out the appropriate sections of PHP.

[emartine]

I will ask this question to my committee tomorrow and give you a response.

[cmerchant]

Keep us posted. Thanks.

[emartine]

After discussion with my colleagues we all agreed that a new level of permissions would be more appropriate. We have folks (DBAs, Web Admins, App Developers, etc.) who have their own servers but we monitor and maintain their servers. We want them to be able to modify and disable their own servers but not modify system level items or do items like scan entire networks, then we have folks that are "power users" that require the ability to modify DBA, Web or App Dev servers but also don't require nor do they have the knowledge to configure nagios or its underlying components/wizards.

[jdalrymple]

How about a request that reads something like this:

User wants CCM roles to be as granular as ability to view/modify only certain hosts/services/hostgroups/servicegroups and would also like the ability to prevent users from running any creat-host type wizards?

[emartine]

That would work.

[jdalrymple]

Added to internal feature request tracker. Locking topic.