Endpoint Operations Management agents include plug-ins that determine which objects to monitor, how they should be monitored, which metrics to collect, and so on. Some plug-ins are included in the default Endpoint Operations Managementagent installation, and other plug-ins might be added as part of any management pack solution that you install to extend the vRealize Operations Manager monitoring process.
You can use the Plug-in tab in the Content view to disable or enable the agent plug-ins that are deployed in your environment as part of a solution installation. For example, you might want to temporarily disable a plug-in so that you can analyze the implication of that plug-in on a monitored virtual machine.
All the default plug-ins and the plug-ins that are deployed when you installed one or more solutions are listed alphabetically on the tab.
You must have Manage Plug-ins permissions to enable and disable plug-ins.
When you disable a plug-in, it is removed from all the agents on which it has existed, and the agent no longer collects the metrics and other data related to that plug-in. The plug-in is marked as disabled on the vRealize Operations Manager server.
You cannot disable the default plug-ins that are installed during the vRealize Operations Manager installation.
You use the action menu that appears when you click the gear wheel icon to disable or enable plug-ins.
Before you deploy a new version of a plug-in, you must implement a shut down method. If you do not implement a shut down method, the existing plug-in version does not shut down so that a new instance is created and allocated resources such as static threads are not released. Implement a shut down method for these plug-ins.
Plug-ins that use third-party libraries
Plug-ins that use native libraries
Plug-ins that use connection pools
Plug-ins that might lock files, which cause issues on Windows operating systems
It is good practice that plug-ins do not use threads, third-party libraries, or static collection.