Click the Start a free trial link to start a 30-day SaaS trial of our product and join our community as a trial customer. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
Thanks for asking your question in the community. There is an existing post on Community that could be related.
Please check it out here:
If you learn anything from that post, please share what you learned as a reply to this post.
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
Would you be able to provide more information?
The Java Agent is added to the startup of the Application it's instrumenting, so a server restart would not affect the agent, as when the application starts , the agent will start with it.
Can you validate that the Appdynamics Java Agent is still part of the Application Java Process, you can check using any command e.g ps aux | grep "javaagent".
It might be possible that the following occurred
1. Java Agent directory itself was removed, or permissions changed with patching
2. Server firewall turned on, blocking the Java Agent from communicating to the Controller
3. Application was patched, which removed the Java Agent startup parameters.