On this page:
You can manage app agents connected to the Controller from the AppDynamics Agents window. Click Settings > AppDynamics Agents > App Server Agents to view information, reset agents, disable agents, and more.
To manage app agents, users must belong to a role with the following Account Level Permission:
Administer users, groups, roles, authentication, etc. View License. View AppDynamics Agents. Use Agent Download Wizard.
By default only Account Owners see the list of the agents in the account. See Roles and Permissions.
If you start an application server with an app agent without specifying the business application, the agent appears in the App Server Agents tab as an unassociated agent. You can associate an agent with an application manually:
From the agents list in the App Server Agents tab, select the unassociated app agent from the list.
In the View menu, click Agents not associated with an Application to filter the list of App Server Agents.
Resetting the app agent causes the agent to register itself with the Controller in the same way it does at JVM or application startup, but without restarting the JVM or application. Resetting the app agent purges in-memory data for the agent. It also applies certain configuration changes to the app agent, such as app agent node property changes.
Resetting an app agent causes the Controller to:
Resetting an agent does not re-instrument or remove existing instrumentation. After a reset, the agent re-registers business transactions and backends and it creates new metrics. You may lose a few minutes worth of data between the reset and re-registration operations.
You may need to reset agents after you have reconfigured business transaction or backend detection and the agent is not applying the updated rules:
An app server agent polls the Controller every minute to check whether the agent is enabled or disabled. Disabling an agent can help you troubleshoot application problems. For example, you don't need to uninstall the agent to compare the difference in overhead between when the agent is capturing data versus when it is not. Disabling the agent does not require you to shut down or restart the application server.
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 an app agents individually, right click the agent and click Enable Selected App Agent or Disable Selected App Agent.
Alternatively, enable or disable app agents individually from the Agents tab on the Node Dashboard:
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 window to keep collecting JVM and JMX metrics such as heap memory, memory pools, garbage collection, and thread count.
Deleting an app agent removes the agent and any associated data from the Controller database. This does not affect the instrumentation of the application server. If the application server is still running with an app agent, or if it is subsequently restarted with an app agent, the agent re-registers and appears again in the Controller.
You can delete an app agent by clicking Delete Agent from System button.
To completely remove an app agent completely so that it does not register again, uninstall it. See the uninstall instructions for your agent's platform under Instrument Applications.