AppD Archive

How to configure Agents and Controller for a small footprint?

CommunityUser
Splunk Employee
Splunk Employee

I want to give AD Pro a try on my Production middleware server but I am concerned that the out of the box configuration might be too large a footprint and would impact the server performance.

I know it is better to have a separate VM to run the Controller but, until we move to our new data center, I have no choice but to install the Controller directly on the Production middleware server. I do have disk space to spare (over 150 GB) but I am more concerned about using too much CPU and HTTP resources.

I would like to install 2 agents to monitor two Tomcat instances.

And I would like to configure the agents and controller to limit the footprint as much as possible, even if this means limiting the functionality that I would have access to. Like maybe there is a way to turn off the Snapshots completely?

For my first go around with this tool, I am only interested to look at the live graphs of heap, CPU, threads, classes, garbage collector and database connections. Like having JConsole on sterioids....this would be enough for me.

0 Karma

Arun_Dasetty
Super Champion

Hi Mike,

We suggest you to do the following changes as you are only focussed on certain to monitor and to reduce the amount of data that agent and controller processes with default agent/controller settings under associated application:

1) We request you to install controller with either demo Or small performance profile as this profile should be enough to monitor two agents as referred in docs: http://docs.appdynamics.com/display/PRO13S/Controller+System+Requirements#ControllerSystemRequiremen...

2) We recommend to either disable other entry points if you are interested in monitoring in only particular entry point and also make sure you have not set aggressive snapshot collection to reduce snapshot collection , by default agent settings are optimized , as listed belowimage.png

image.png

image.png

3) If you are not interested in monitoring Business transaction then you can disable agent by toggling on/off button in node dashboard as listed in below screenshot, diabling agent will not monitoring any BTs or custom rules but still will send JVM related statistics like (heap , GC data etc) under Memory screen:

image.png

Let us know if that information helps.

Regards,

Arun

Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...