Disabling an app agent stops the agent from reporting metrics to the Controller. Disabling an agent can help you diagnose agent installation or application issues. It also lets you compare the difference in overhead between when the agent when capturing data versus when it is not, for example, without removing the agent. Disabling the agent does not require you to shut down or restart the application server.

Disabling an app agent does not stop the agent from operating or remove the bytecode instrumentation added by the agent. To fully remove the agent including remove bytecode instrumentation, follow the steps to uninstall the app agent or fully disable agent instrumentation under the Install App Server Agents page specific for the agent type. Uninstalling an app agent or fully disabling an app agent in this manner typically requires an application restart.

All agents connected to the Controller count against the agent license limits for that Controller. Even though it only reports minimal app server-related data, a disabled app agent is still connected to the Controller and consumes an app agent license.

To enable or disable all the app agents for a business application, the App Server Agents tab, click Enable Agents or Disable Agents.

You can enable or re-enable individual agents by selecting them and clicking Enable Selected App Agent or Disable Selected App Agent. Alternatively, enable or disable app agents individually from the Agents tab on the Node Dashboard:

• To disable the agent, click Agent is Off.
• To enable the agent, click Agent is On.

  It takes about a minute for the operation to take effect.

By default turning the agent Off completely disables monitoring. For Java agents, un-check Disable all monitoring including JVM and JMX metrics on the Disable. This App Agent pane to continue collecting JVM and JMX metrics such as heap memory, memory pools, garbage collection, and thread count.