Beginning in February 2020, AppDynamics switched from Semantic Versioning to Calendar Versioning for some agents and the first deployments of SaaS Controllers. In March 2020, the entire product suite will use Calendar Versioning.

Skip to end of metadata
Go to start of metadata

Related pages:

Your Rating:
1 Star2 Star3 Star4 Star5 Star
23 rates

View Details

Using an AppDynamics Administrator account, click Settings > AppDynamics Agents > Machine Agents to see details and manage your installed Machine Agents.

  • Hostname: The name of the machine on which the agent is installed.
  • Version: The version of the installed Machine Agent software. 
  • Applications: The name of the application with which the agent is associated. 
  • Enabled: Whether the agent is enabled.

Available Actions

Reset Selected Machine Agent

Restarts the selected Machine Agent and runs it with any updated configuration files on the agent host and any changes made on the Controller that affect the agent. The reset functionality works only for pre 4.2 Machine Agents.

View Machine

Shows summary details about the Machine Agent as follows:

  • Name: The name of the machine on which the agent is installed.
  • IP Address: The IP address of the machine on which the agent is installed.
  • OS: The operating system running the agent.
  • Status: This field displays the following information: Initialized
  • Install Time: Date and time agent was installed.
  • Last Start Time: Date and time agent was last restarted.

Disable and Enable Agents

Disabling the agent temporarily suspends its collection of metrics. The agent can be quickly re-enabled when you want. 


You must have the application-level permission, configure agent properties to enable and disable agents.

When the Standalone Machine Agent is disabled, the agent stops reporting hardware metrics and metrics from any extensions installed on the agent until you re-enable it.  The disabled Standalone Machine Agent no longer reports events and any installed extensions are also stopped. While disabled, the agent continues to consume a license. The agent maintains a 'heartbeat' connection to the Controller so that it can be 'enabled' again quickly. The agent persists its enabled/disabled state even after the Standalone Machine Agent is restarted. Once re-enabled, all normal Standalone Machine Agent activities resume.

Delete Selected Machine Agent

The purpose of the delete functionality on the admin page is to delete the underlying machine metadata for an orphaned machine. A machine is considered "orphaned" when it is no longer associated with any APM nodes or with Server Availability. You can not delete a machine that is not an orphan. To delete a machine that is not an orphan, you must first delete all nodes on that machine and delete the machine from the Servers list. You can select multiple machines for the delete action.

You can also delete a machine agent from the Servers List. Note the following:

  • Server Visibility Administrator permission is required to delete machines.
  • You can delete machines from the Servers list regardless of whether they have Server Visibility enabled. You can select multiple machines for the delete action.
  • Deleting a machine from the Servers list deletes the underlying machine metadata that displays on the AppDynamics Agents Admin page, but only if no APM nodes are currently associated with the same machine.
  • Deleting a machine that still has APM nodes currently associated with it removes the entry from the Servers list, but retains the underlying machine metadata. That information continues to be displayed on the AppDynamics Agents admin page.

  • No labels