AppDynamics Application Intelligence Platform
You can manage the app agents that are connected to the Controller from the App Server Agents administration page. From this page, you can view information about an app agent, disable an app agent, reset an app agent, and more.
There are two ways to access the page:
AppDynamics lists all agents for all business applications by default.
If you start an application server with an app agent without specifying the application with which it is associated, the agent appears in the app agents list as an unassociated agent. You can associate an agent with an application manually from the App Agents administration page.
From the Agents list in the App Server Agent panel, select the unassociated app agent from the list.
If you have a long list of agents, you can choose Agents not associated with an Application from the View dropdown men in the upper right corner to display only app agents that are not currently associated with an application.
Resetting the app agent purges all existing data for the agent, including metrics and discovered transactions. You do not need to restart the application server to reset agent data.
After you have reconfigured business transaction or backend detection, you may need to reset the agents. If new detection rules are not detecting newer transactions or backends:
Resetting an app server agent causes the Controller to:
Resetting an agent flushes the in-memory business transactions, exit calls, and registration information for the agent. It does not re-instrument or remove existing instrumentation.
After a reset, the business transactions and backends are re-registered and new metrics are created.
You may lose a few minutes worth of data between the reset and re-registration operations.
An app server agent polls the Controller every minute to check whether the agent is enabled or disabled. If an App Agent for Java is disabled, it stops capturing all data except for JVM JMX metrics such as heap memory, memory pools, garbage collection, and thread count.
Disabling an agent can help with troubleshooting. For example, it lets you easily compare the difference in the agent's run-time overhead when capturing or not capturing data, without going through the trouble of uninstalling the agent. Disabling the agent does not require the application server to be shut down or restarted.
All agents connected to the Controller count against the agent license limits for that Controller. Since a disabled agent is still connected to the Controller, even though it only reports minimal app server-related data, it still occupies an agent license for the Controller.
To activate the agent, click Agent is On.
Deleting an app agent in the AppDynamics Agents window 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 database and in the UI..
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.
See Node Dashboard.
By default only Account Owners see the list of the agents in the account.
You can create a custom administrator role that grants this account-level permission. See Configure Roles.
Keep in mind that this also grants that role general administrator rights, including the permission to administer users, roles, authentication, etc. There is no way to grant permission only to view agents.