On this page:
A machine has a Standalone Machine Agent and an App Server Agent running together, but the agents report to different nodes. When you look in the Metric Browser, for example, application metrics appear under node abc but machine metrics appear under node abc.mydomain.com.
Make sure that the <unique-host-id> on the Standalone Machine Agent matches the
<unique-host-id> for the App Server Agent:
(not associated with any applications), you need to set the <unique-host-id> for the Standalone Machine Agent to the same ID used by the corresponding App Server Agent. This ensures that both agents report metrics to the same node.
Linux and Unix-like systems
To identify which process is running the machine agent, use the following command:
In the Windows Services Application, look for the AppDynamics Machine Agent service.
When a 32-bit JRE is used with 64-bit operating system, you may see values of zero for disk and network metrics. To solve this problem, use a 64-bit JRE with the 64-bit operating system.
The Machine Agent monitors a particular machine (also called "host server") and not a particular application server. The machine agent can therefore report to multiple nodes running on the same machine. A flow map, on the other hand, displays the communication between different nodes during application execution, or the business transaction flow from tier to tier. A Machine Agent cannot be a part of the flow and therefore is not shown in the flow map.
Health rule violations based on metrics monitored by the machine agent are included in the health indicator on the various application, tier, and node dashboards. The health indicator is driven by health rule violations in the given time period configured on hardware metrics collected by the Machine Agent. Some health rules are configured by default. To configure additional health rules, see Configure Health Rules. For more details on Server Availability and health rules, see Configure Machine Health Rules, Policies, and Alerts.