This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
49 rates

If you have different applications running on the same machine, to get hardware metrics for each application, run separate Standalone Machine Agents on the same machine.

Unique Host ID Property

When an app agent runs on the same machine as a machine agent, configure the same uniqueHostId property value on for both the app agent and the machine agent. If there are multiple app agent/machine agent pairs on the same host, each pair should have a different uniqueHostId property.

When different tiers in the same application are associated with different machine agents, configure a different uniqueHostId property for each app agent-tier/machine agent pair.

To retain historical data if the nodes are moved to a different machine, use the hostname of the old machine from which the nodes were moved as the UniqueHostId parameter when you configure the app agent/machine agent pair on the new host. For example, if the hostname of the original machine was "12345.sample.com", on the new host start the app agent and the machine agent with:

-Dappdynamics.agent.uniqueHostId=12345.sample.com

Configuring Multiple Standalone Machine Agents

The following instructions assume two applications and two standalone machine agents on a single machine, but they can be interpolated to cover more than two.

To configure two Standalone Machine Agents for two applications running on the same machine

  1. Download two copies of the Standalone Machine Agent, one for each application.
  2. Assign the standalone machine agents different names, for example: "MachineAgent1" and "MachineAgent2".
    If there are custom scripts running on the standalone machine agents, they must not use the same resources.
  3. Configure the first application/machine agent pair for the first application:
    1. Delete the app agent node from the Controller UI.
    2. Configure the applicationName and uniqueHostID properties for the app agent.
    3. Configure the applicationName and uniqueHostID properties for the machine agent using the same application name and unique host id values that you used for the app agent configuration.
  4. Configure the second application/machine agent pair for the second application:
    1. Delete the app agent node from the Controller UI.
    2. Configure the applicationName and uniqueHostID properties for the app agent. These values must be different from the values used for the first application.
    3. Configure the applicationName and uniqueHostID properties for the Standalone Machine Agent using the same applicationName and uniqueHostId values that you used for the app agent configuration.
  5. Restart all JVMs.

Sample Configuration

The following image shows a sample configuration of two physical machines with two applications each. In it: 

  • Machine1 runs App1, which is instrumented with one app agent (AppAgent1) and one Standalone Machine Agent (MachineAgent1).
  • Machine1 also runs App2, which is instrumented with one app agent (AppAgent2) and one Standalone Machine Agent (MachineAgent2).
  • Machine2 runs App1, which is instrumented with one app agent (AppAgent3) and one Standalone Machine Agent (MachineAgent3).
  • Machine2 also runs App2 is instrumented with one app agent (AppAgent4) and one Standalone Machine Agent (MachineAgent4).

Given this deployment, the Controller would report separate metrics for each of Machine1_App1, Machine1_App2, Machine2_App1, and Machine2_App2.

  • No labels