KickStarter Series 15 Minutes Introduction to AppDynamics
©Karun Subramanian 6
The controller is the engine of AppDynamics. It receives monitoring data from Agents installed on the
Application servers (or Database Servers, Web Servers etc). The user accesses and manages the
monitoring data by connecting to the Controller via web browser (usually at port 8090). It helps to
understand the terminology used in AppDynamics to know how it works.
Node
A node is a monitored Server or JVM (or CLR). Typically the node corresponds to an individual
Application Server (Physical or Virtual)
Tier
A tier is a logical grouping of nodes generally relating to a particular business function. Note that an
agent cannot belong to more than one Tier
Business Application
A Business Application is the top level container in AppDynamics. It contains Tiers. Role Based Access
Controls in the Controller UI are implemented at the Business Application Level
Backends
Backends are any external systems to the AppDynamics agent that are not instrumented. For example,
if a .NET Application that is instrumented makes a call to a SQL Server Database Server, if the SQL
Server is not instrumented with AppDynamics agent, it is considered a ‘backend’ in the .NET
application. The response time for the backend calls are recorded (along with load, errors etc).
However, deeper level metrics are possible only when the remote system is instrumented.
AppDynamics automatically recognizes most of the popular backend systems.
How can I get started, really?
In order to get the taste of AppDynamics, you can get started for free. At a high level, here is what you
have to do:
1. Identify a Server that can serve as AppDynamics Controller. Controller is available for the
following platforms
Windows (32 and 64 bit)
Linux (32 and 64 bit)