Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. 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.
What are you looking to achieve by stopping the agent?
I appreciate your quick response. In case we feel that the app agent is causing performance impact to the running application, then we should be disable the java agent. Is it possible to detach agent without killing the running application process?
You can stop the agent from collecting and reporting data as described here: https://docs.appdynamics.com/display/PRO45/Manage+App+Agents#ManageAppAgents-EnableandDisableAppAgen...
It goes without saying that the agent should not impact application performance, and if you find that it is you should work with support to figure out why.
A common source of "agent overhead" arises from increased pressure on the garbage collector, in cases where the agent has been added to the process with insufficient headroom available in the heap.
There is no way to totally detach the agent (uninstrumenting all the instrumented classes would obviously place more load on the JVM, so it's not clear that total removal of the agent would be a good move when under performance pressure)