Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: DOCS-4084 Customer reported: https://docs.appdynamics.com/display/PRO45/FAQs+and+Troubleshooting#FAQsandTroubleshooting-sma_unique_id_of_app_agen

...

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

Resolution

 First, check to see if the hostnames match. If they don't:

...

  1. Click the gear icon () in the Controller menu and choose AppDynamics Agents.
  2. Select the Machine Agents tab.
  3. Check the Applications field for the agent name. 

    In addition, for consistency in naming in the Servers tab, use the <machine path> attribute to set the hostname. By using the machine path, you don't have to use the fully qualified domain name (FQDN) for some agents, and the hostname for others. The reported hostname is still available to view by checking the option in the Agents Admin view. 

  4. Check the ID for the App Server Agent:
    1. Go to the App Server Agents tab.
    2. Search for the App Server Agent to which you want to associate the Machine Agent.
    3. Check the Unique Host ID field for the App Server Agent installed on that machine.  
  5. Set the <unique-host-id> for the Machine Agent to the same <unique-host-id> as the App Server Agent.
  6. Restart the Machine Agent to apply the previous changes. Your Agents will appear as associated after a few minutes

Anchor
id_agent_process
id_agent_process
Identify the Standalone Machine Agent Process

...