AppDynamics Application Intelligence Platform

3.9.x Documentation


Learn by Watching

Doc Maps

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: fixed table - removed line next to it. This table was copied from GMAIL and it's div class gmail gave it the line. I had to recopy the table and paste it back in to get rid of the line.


This cheatsheet lists the steps required to get a basic AppDynamics installation, suitable for demos and small performance profiles. These steps typically take a few hours, excluding any process delays for provisioning servers or making other infrastructure changes.


The AppDynamics solution requires a central Controller. It can be hosted as SaaS by AppDynamics or you can install it on-premise.

On-Premise Controller Requirements

For an on-premise Controller, the controller configuration required depends on the number of JVMs to be monitored.  Requirements for the small profiles are:


Supported OS platformsCPU # of coresRAMDisk storageDisk I/O 
write/read/random read
Agent Count*Metrics Count/minute
DemoLinux (32 & 64-bit) 
Windows (32 & 64-bit)
2 CPU Cores  
1.5 GHz minimum
2 GB50 GB50 MB/sec 
50 MB/sec 
1.5 MB/sec
up to 55 K max
SmallLinux (32 & 64-bit) 
Windows (32 & 64-bit)
4 CPU Cores  
1.5 GHz minimum
4 GB100 GB50 MB/sec 
50 MB/sec 
1.5 MB/sec
6-1025 K  max

AppDynamics for Databases Requirements

AppDynamics for Databases is an on-premise solution and can be installed on the same server as the AppDynamics Pro Controller, or on a different server.  In either case it requires 1 CPU and 2GB of RAM to monitor a single database instance. If you install it on the Controller server, these resources are in addition to the Controller resources. Also, change the default port number so it doesn't conflict with the Controller. See Prevent and Resolve Port Number Conflicts.



AppDynamics requires the following network configurations:

  • Every app agent, and therefore every server on which an agent is installed, needs to be able to communicate with a Controller using HTTP(S) on a port of your choosing (8090 and 8091 are the defaults). For SaaS, use 80 or 443.
  • Browsers used to view the AppDynamics UI need access to the Controller on one or both of those ports.   
  • (On-Premise) The Controller must be able to access the internet on port 443 to enable AppDynamics' End User Monitoring feature, because it retrieves aggregated web view stats from
  • AppDynamics for Databases must be able to connect as a JDBC client to the database to be monitored, and be accessible on its HTTP listen port from browsers used to view its UI.
  • Any load balancers between Java components in the network must not strip the AppDynamics correlation headers from the HTTP traffic.

Getting Started

There is a getting started guide in the documentation.  In summary, you:

At this point, AppDynamics should be configured and monitoring all traffic flowing through the application.