Cisco AppDynamics Community

Neha.Dev · ‎02-23-2021

The java agent was installed and it was reporting fine, but last week the server was down , and after the patching work was done, it was not reporting in AppD. AppD did not come back up when the server came back up.

Please suggest.

Ryan.Paredez · ‎02-23-2021

Hi @Neha.Dev,

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.

Thanks,

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.

Mario.Morelli · ‎02-24-2021

Hi Neha

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.

Ciao

Found something helpful? Click the Accept as Solution button to help others find answers faster.

Liked something? Click the Thumbs Up button.

Learn more about me in the Community Member Spotlight Q & A

Cisco AppDynamics Community

Java agent not reporting in appd controller after the finished patching.