Splunk AppDynamics

Upgrading app server agents

Hari_Shree_Josh
Explorer

We are having issues with an app agent on one of the nodes of our instrumented application. Its status keeps dropping down to 0% and comes back up once it is reset. The support team advised us to upgrade the agent's version as the current version is outdated (v 4.0.4.0).

Now I cant find a relevant article in the documentation on how exactly it can be done. Do we need to install the app server agent again or is there a way to upgrade them through a wizard or something?

 https://download.appdynamics.com/download/prox/download-file/sun-jvm/4.5.17.28908/AppServerAgent-4.5...

Thanks.

Labels (3)
0 Karma

Mika_Sasaki1
Explorer

Thanks for posting the question on the Community.

To upgrade the AppDynamics Java Agent, you simply copy the existing agent directory to a backup location and replace it with the new agent directory. You then copy configuration file changes made in the old directory to the new agent directory and restart the application server.

Unfortunately, no upgrade wizard available in Java App Server agent.
Please refer to the following URL for the detailed procedure:
https://docs.appdynamics.com/display/PRO45/Upgrade+the+Java+Agent

Let me know if this helped you.

Many thanks,
Mika

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...