This page describes scenarios for new standalone Machine Agent installations.
APM Machine Agent Installation Scenario
This scenario contains a host server running one or more instrumented applications and one Machine Agent. When you install the Machine Agent on the same server with any app agent, do not specify the application name and tier name. The one Machine Agent reports the hardware metrics to each node where the app agent and the Machine Agent have matching host IDs.
If you plan to enable Server Visibility on a Windows server where a .NET APM agent is installed, you must enable .NET Compatibility Mode on both the Controller and the Machine Agent. See .NET Compatibility Mode
Version 4.3 and later includes one Machine Agent license with each APM app agent. You can install this Machine Agent only on the same server with the app agent.
Independent Machine Agent Installation
This scenario contains a host server running only the Machine Agent without app agents. You do not need to specify an application or tier. You can view the Machine Agent metrics from the Servers list or the metric browser. This scenario requires a Server Visibility license.
Version 4.3 and later requires a Server Visibility license for a Machine Agent installation.
If you are doing an Independent Machine Agent installation and you want the hardware metrics reported to nodes in an application, then you must configure the application name and tier name where you want the metrics to appear. The node name defaults to Node1 for the machine.
Using the values for the application name and tier where you want to see the metrics reported, configure these properties:
- application name
- tier name
- uniqueHostId for both the machine agent and app agent: use the same value
Unique Host ID Property
The uniqueHostId property is not required. However, if you do define a uniqueHostId, then the Machine Agent uses the Java API to retrieve the host ID. The results from the API can be inconsistent. The same JVM may return a different value for the same machine each time you restart the Machine Agent. As a workaround, Appdynamics recommends that you set the value of uniqueHostId to the host ID that you want to see in the UI. Use the same value for uniqueHostId for the App Agent.