You have the ability to blacklist certain plugins from ever being run by the agent. This can be useful if you don’t want to see warnings about certain plugins requiring more configuration which you don’t intend on enabling. A common example of this is Apache’s extended status module. To blacklist a plugin, follow the instructions below:

Linux

To create a plugin blacklist for a Linux Agent, you will need to add a line to the Agent configuration file.

• /etc/fm-agent/fm_agent.cfg

Under the [AgentConfig] section of this file, add the following:

plugin_blacklist = [plugin textkey list]

Replacing the [plugin textkey list] with a comma-separated list of plugin textkeys. To find out what plugin textkeys to use, you can run the following command:

• ls /usr/lib/fm-agent/plugins/

This will list out all of your Agent’s plugins. The plugin textkey is just the name of the plugin’s file without the .py ending.

Now the Agent will no longer check on the configuration status of the services related to the plugins that you have placed on your blacklist.

Windows

To create a plugin blacklist for a Windows Agent, you will need to add a line to the Agent configuration file (C:\Program Files (x86)\FortiMonitorAgent\Agent.conf). Within the tags of this file, add the following:

<add key="PluginBlacklist" value="[resource category list]" />

Replacing the [resource category list] with a comma-separated list of resource categories. To find out what resource categories to use, you can reference the list found within the tags of the configuration file that you are editing.

Once you have done this, restart the panopta-agent service. For instructions on how to that see this page for reference. Now the Agent will no longer check on the configuration status of the services related to the plugins that you have placed on your blacklist.