AppDynamics Application Intelligence Platform
3.9.x Documentation
Page History
...
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.
Infrastructure
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:
| Controller performance profile | Supported OS platforms | CPU # of cores | RAM | Disk storage | Disk I/O write/read/random read | Agent Count* | Metrics Count/minute |
|---|---|---|---|---|---|---|---|
| Demo | Linux (32 & 64-bit) Windows (32 & 64-bit) | 2 CPU Cores 1.5 GHz minimum | 2 GB | 50 GB | 50 MB/sec 50 MB/sec 1.5 MB/sec | up to 5 | 5 K max |
| Small | Linux (32 & 64-bit) Windows (32 & 64-bit) | 4 CPU Cores 1.5 GHz minimum | 4 GB | 100 GB | 50 MB/sec 50 MB/sec 1.5 MB/sec | 6-10 | 25 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.
Network
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 agg.eum-appdynamics.com.
- 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:
- (For On-Premise) Install the AppDynamics Controller on the server provided for it and apply the license file
- Install the Java Agent, Install the .NET Agent, Install the PHP Agent, and Install the Node.js Agent
- Enable End User Monitoring in the Controller
- Add the javascript EUM agent to the application's web pages
- Install AppDynamics for Databases on the server provided for it
- Add a collector for your database instance(s)
- Configure the integration between AppDynamics and AppDynamics for Databases
- Install the Standalone Machine Agent to get additional infrastructure metrics and to use a monitoring extension.
At this point, AppDynamics should be configured and monitoring all traffic flowing through the application.
Overview
Content Tools
Apps