Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on 06-28-2017 10:20 AM
A legacy Machine Agent and Java Application Agent are installed on a machine. Despite correct installation and configuration, one or both of the Agents do not report. The first step in troubleshooting this issue is to validate the Unique Host ID, which is a problem more common with Machine Agents.
Machine Agents use the Java API to get the Unique Host ID. Sometimes the same JVM can return different values for the same machine each time the Machine Agent is restarted. One possible cause is the Unique Host ID of the App Agent and the Machine Agent are not in sync. In this case, the Machine Agent does not know which application to register.
If there is any discrepancy between the two Agents, resolve the issue by providing the same Unique Host ID value for the App Agent and the Machine Agent using the following steps.
Note: If it is not feasible to stop the App agent, it is possible to sync the Unique Host ID value of the Machine Agent with the App Agent, and then apply the property to the App Agent on the next restart.
-Dappdynamics.agent.uniqueHostId=<your-host-id>
system property-Dappdynamics.agent.uniqueHostId=<your-host-id>
system property<unique-host-id>your-host-id</unique-host-id>
element within the <machine_agent_install>/conf/controller-info.xml
file.ok i wound up deleting the app in appd controller and re-creating it with the settings and then that worked - thanks
@James.Pace , thank you for sharing what worked for you.
Claudia Landivar
Community Manager & Editor
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form