Splunk AppDynamics

How do I stop java agent that was attached to a running java process?

CommunityUser
Splunk Employee
Splunk Employee
 
Labels (1)
0 Karma

Peter_Holditch
Builder

Bijal,

What are you looking to achieve by stopping the agent?

Warm regards,

Peter

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Peter,

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?

Bijal

0 Karma

Peter_Holditch
Builder

Bijal,

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)

Warm regards,

Peter

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thank you for the information and the link. This helps!

Bijal

0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...