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

    You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    « Previous Version 22 Next »

    On this page:

    Works with: 


    Your Rating:
    1 Star2 Star3 Star4 Star5 Star
    3 rates

    Application Analytics deployment options vary based on several factors, such as which data you would like to monitor and your Controller deployment. This topic covers all of your deployment options. 

    Deploy without an Analytics Agent

    You do not need to configure an Analytics Agent to capture the following.

    Transaction Analytics Only for Java Applications

    If you only capture Transaction Analytics for Java applications, you can configure Transaction Analytics without a dedicated Analytics Agent. Make sure you meet the following requirements:

    • Java Agent version 4.5.15 and later 
    • Controller version 4.5.16 and later
    • Sufficient Transaction Analytics licenses

    In this deployment model, Analytics retrieves data directly from your app agent. The data is then reported to the Events Service and later the Controller. Therefore, no separate Analytics Agent is required.

    Make sure your system can connect to the Controller and Events Service to send Analytics data. You can proceed to Collect Transaction Analytics Data

    Browser and Mobile Requests and Sessions Data

    You do not need to install any agent-side Analytics components. The EUM processor passes data to Analytics automatically.

    Deploy with an Analytics Agent

    The sections below discuss the requirements to deploy the Analytics Agent. You need to configure an Analytics Agent to capture data in the following scenarios:

    Transaction Analytics Only 

    You need an Analytics Agent to capture Transaction Analytics for:

    • Java Agents version 4.5.15 and earlier
    • Any version of .NET, Node.js, and PHP Agents 
    • Controller version 4.5.15 and earlier 

    To configure Transaction Analytics:

    • Download and install either the Standalone Machine Agent or the Analytics Agent (standalone binary) on each machine. You can also use a shared Analytics Agent instance.

    • Enable the app agent Analytics Dynamic Service.

    Log Analytics Only

    To configure Log Analytics:

    Transaction and Log Analytics

    To configure Transaction and Log Analytics:

    • Install either the Standalone Machine Agent or the Analytics Agent (standalone binary) on the machine.

    • Enable the app agent Analytics Dynamic Service.

    SaaS vs On-premises Analytics Configuration

    When you deploy Analytics with the Analytics Agent, the configuration requirements differ based on your deployment:

    • The Events Service is provided as part of the SaaS service. AppDynamics stores the data and hosts the server components of the system for you. You install only the Analytics Agent components of the system. This is described in the section Agent Side Components.
    • For on-premises, you host the components yourself, storing all data on-premises. This means you need to install the Agent Side Components and the Controller and Events Service components described in Controller Deployment and Events Service Deployment. The on-premises deployment involves additional setup and administration, but it enables you to retain the analytics data within your own data center.  

    Separate Host for the Analytics Agent

    If your Analytics Agent is on a host separate from the monitored application, see Remote Analytics Agent Sizing. 

    Connect App Agents to the Events Service

    You can retrieve Transaction Analytics data through Java Agent versions 4.5.16 and later without the need for a dedicated Analytics Agent. In this deployment model, the Java Agent communicates with the Events Service directly. For most deployments, this communication occurs automatically as long as you have the correct agent version. See the appropriate documentation to ensure your deployment can connect to the Events Service:

    Identify Internal Events Service Endpoints 

    AppDynamics uses connection URLs to connect the Events Service to the Controller and app agents. The URL used for the Controller-Events Service connection may be different than the URL used for the app agent-Events Service connection. For example, SaaS deployments use internal URLs for the Controller-Events Service connection. 

    If your deployment uses different URLs for each connection, you need to provide the Controller-Events Service URL as an administrator property. This allows your app agent to find the Events Service endpoint. 

    To connect the app agent to an internal Events Service URL:

    1. Log in to the administration console: 
      http:<controller-hostname>:8080/controller/admin.jsp or https:<controller-hostname>:45/controller/admin.jsp
    2. On the Controller Settings page, navigate to the analytics.agentless.event.service.url property and input your Controller-Events Service endpoint. 
    3. Press Save
    Connection Ports

    For SaaS-based installations, the connection between the Java Agent and the Events Service in the cloud takes place over ports 80 (HTTP) and 443 (HTTPS). For on-premises installations, the port on which the Events Service receives data from the Java Agent is configured during installation.

    If you have network policies that may prevent this connection, such as firewalls, you need to configure the policies to connect with the Events Service. See Agent-to-Controller Connections for more information.  

    Enable SSL

    See Enable SSL for the Java Agent if you use a custom trust store for the Java Agent.  

    Proxy Connection

    See Java Agent Configuration Properties if your proxy connection encrypts agent credentials.

    Adjust Configuration Properties

    The Java Agent can be configured to handle higher loads if necessary. Contact AppDynamics Support to tune these properties. 

    • No labels