This topic describes scenarios for new installations.
For upgrades from pre-4.2 versions, see Upgrade the Standalone Machine Agent.
To consolidate pre-4.2 installations that have multiple machine agents on one server, see Consolidate Multiple Machine Agents.
APM Machine Agent Installation
This scenario is 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, you should not specify 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. For more information, see .NET Compatibility Mode.
Version 4.2 and higher includes one machine agent license with each APM app agent. This machine agent can only be installed on the same server with the app agent.
Independent Machine Agent Installation
This scenario is a host server running only the machine agent and no app agents. It is not required to specify an application and tier in this case. The Machine Agent metrics can be viewed from the Servers list or the metric browser. This scenario requires a Server Visibility license.
Version 4.2 and higher requires a Server Visibility license for an Independent Machine Agent Install.
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.
Configure the following properties using the values for the application name and tier where you want to see the metrics reported:
- 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 don’t define a uniqueHostId the Machine Agent uses the Java API to get the host ID. The results from the API can be inconsistent and in fact, the same JVM can sometimes return a different value for the same machine each time the machine agent is restarted. To avoid problems of this nature, we recommend 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.