On this page:
Installing an AppDynamics app agent can be a manual process for small environments with just a few monitored applications, or an automated process for an environment with a large number of agents or if you need to deploy agents on an ongoing basis. The following sections provide references for each approach, along with general information on installing AppDynamics app agents.
For information on manually installing agents, see the following links.
- For Java application monitoring, see:
- For .NET application monitoring, see:
- For PHP application monitoring, see:
- For Node.js application monitoring, see
For automated deployment guidelines, see Deploy AppDynamics.
Network Requirements for App Agent Deployment
The following guidelines can help you estimate how much bandwidth overhead will be added to your environment by deploying AppDynamics agents.
Keep in mind that the exact bandwidth required for a deployment varies greatly depending on the nature of your application, the agent configuration, and the AppDynamics features you use. The best way to determine the bandwidth overhead is to test the AppDynamics deployment in a staging environment that mirrors as closely as possible the live operating environment.
- The approximate bandwidth used by a single Java Agent with the default configuration is 5 to 8 kilobytes per second.
- Scaling of additional agents is linear. That is, if the average bandwidth usage for an app agent in a given deployment is 5 kilobytes, adding 10 means that bandwidth usage will be 5 × 10, or 50 kilobytes.
- While the average bandwidth used is 5 to 8 kbytes per second, agents send data to the Controller in bursts rather than as a steady stream of data. When testing bandwidth usage, to determine the actual kbytes per second used by an agent, you need to observe and average out traffic over the course of at least several minutes.
- When testing bandwidth usage in the environment, keep in mind that different types of tiers will generate a different amount of load. For instance, a database tier tends to generate more traffic between the agent and Controller than an application server tier. For the best possible estimate, the test should take this into account.