Provide ability to disable Agent's plugins when needed

Please provide the ability to disable Agent's plugin when needed. We installed the Agent on a few servers, and we are stuck until they are rebooted... Rebooting those servers is not something that could be done without causing pain...

In our case, most of those plugins wont be used for this particular setup. Especially the NetPath Agent which is the one blocking us in this case. Winpcap is already installed and running on the machines, I don't want this to interfere with the Server's production application, especially if we have no plan to use this agent for NetPath.

Find more posts tagged with

agent configuration

NetPath

orion agent

Status: None

Comments

aLTeReGo

The basic agent functionality should continue to function normally when the NetPath plugin or its dependencies require a reboot. The only time the agent should actually require a reboot to function for node/application monitoring is if the .NET Framework has been upgraded on the machine.

planglois

I cannot use the "Edit Node" button on a node where the agent status is "Plug-in error"...

I cannot also list or manage Node's ressource list :

This error prevents me to change anything (like Caption or node's custom properties) on that page and submit. ( )

I've found out after creating this Idea that the NetPath plugin crashed our app on a server, by trying to reinstall Winpcap where it was already there and running... So much for resiliency...

Sorry aLTeReGo, I wasn't clear enough in the description. When I was talking about system reboot it was regarding fixing the installation in our case. Still, in the 3 nodes listed in the first screenshot, I cannot change anything in the Edit node page even if the agent has a "Reboot Pending" state:

Question: Can we prevent the installation/use of some plugin in any ways? How can I make sure another Winpcap library wont be used where incompatible?

Also, while I have you, is the Agent Status listing in the "Manage Nodes" page is fixed in later versions? (we are currently running NPM 12.0.1 / SAM 6.3.0 / Core 2016.2.100)

My guess is that 1 = OK, 5 = Reboot pending, 11 = Plugin error.