AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    This page provides a selection of topics to consider when deploying AppDynamics, from available on-premises platform architectural models to AppDynamics agent installation and administration. 

    About AppDynamics Deployment

    When starting out with AppDynamics, you may want to deploy in a small-scale demonstration environment. Deploying AppDynamics to a full production environment introduces complexity, such as increased scale, with possibly hundreds of applications that monitor non-traditional running environments, virtualized systems, and complex network topologies.

    AppDynamics was designed to handle this complexity with virtualized support and tools to maintain large-scale AppDynamics Agent deployments.

    Deployment Models

    The Controller is the core of an AppDynamics deployment and uses installed agents to collect data from a monitored environment. The Controller UI is where you can view, understand, and analyze the data. 

    SaaS Deployment

    The AppDynamics SaaS deployment is a cloud-based solution that enables real-time visibility into the health and performance of your instrumented environment, with significantly reduced cost and maintenance. With a SaaS deployment:

    • AppDynamics manages the server-side components of the AppDynamics Platform, including its installation and upgrades.
    • There is no need for you to install the Controller.
    • You enjoy lower total costs, guaranteed availability, data security, significantly reduced maintenance, and automatic upgrades.

    On-Premises Deployment

    In an on-premises deployment, you install and manage all platform components. The first step is to download the Enterprise Console, which is the installer for the Controller and Events Service. You can use it to install and manage the entire lifecycle of new or existing on-premises platforms and components.

    To get the Enterprise Console:

    1. Start a free trial.
    2. Download the Enterprise Console from the AppDynamics Download Portal.

    For information on on-premises installations, see AppDynamics Application Performance Monitoring Platform


    Network Port Requirements

    To deploy AppDynamics, you may need to modify the configuration of network components to permit access to ports used in the AppDynamics deployment. The following pages describe the specific ports used in the system: 

    Deployment Planning Roadmap

    See Getting Started to begin with a trial or investigatory installation of AppDynamics. For a minimal installation, you can easily get AppDynamics up and running in an hour or two. Deploying to a production environment, however, usually adds considerations to the initial installation process. You might have security, network, and change management requirements governed by your organizational policies.

    This section outlines the typical production roadmap divided into several broad categories. Depending on your goals, the size of the deployment, and many other factors, you may want to combine/separate specific steps, as best you see fit for your environment.   

    Plan the Controller and Platform Installation (on-premises)

    1. Determine your deployment profile: small, medium, or large.
    2. Follow the hardware sizing guidelines for your profile.
    3. Discover network layout, bandwidth, and connectivity. View the port connections required for the AppDynamics components you are installing and address network requirements to permit the connections. 

    Plan for Security

    1. Determine the access control strategy for UI users, including locally authenticated users and externally authenticated users (LDAP, SAML, and so on).
    2. Determine SSL requirements and key management.

    Define Controller operating procedures (on-premises)

    1. HA setup (via Enterprise Console).
    2. Failover methodology (scripted, automated).
    3. Data backup strategy (hot, cold, or LVM, frequency, the storage required, metadata backup).

    Devise Agent rollout strategy

    1. Manual, automated, or scripted.
    2. Integrating rollout with your application deployment process.

    Plan AppDynamics Model

    1. Understand how your application maps to the AppDynamics concept of application, tier, and node. Determine the naming strategy for the model.
    2. Devise Business Transaction strategy. Determine which end-to-end business processes in your environment you want to monitor as Business Transactions.
    3. Devise End User Monitoring and Analytics data collection strategy.
    4. Consider database and hardware monitoring strategy. 

    Users who will access AppDynamics

    1. Identify monitoring team or others who will administer AppDynamics. Ensure that they can maintain it, both from a resource and skill-set standpoint. 
    2. Identify stakeholder from each group that will use AppDynamics. 

    Define monitoring strategy

    1. Assess the alert and health rule strategy that makes sense for your requirements.
    2. Define reporting strategy. 
    3. Determine integration points with other systems (using extensions or REST API).
    • No labels