Discussion Feed

By default, the number of BTs is set to 200 BTs per application and 50 BTs per agent. After the first 50 agents per agent are registered, additional BTs discovered from traffic will flow to a virtual business transaction named All Other Traffic - tier_name.   If the overall BTs registered for the application are below 200, you can choose to increase the default value of BTs discovered per agent using the agent node property: max-business-transactions (link:  https://docs.appdynamics.com/pages/viewpage.action?pageId=104015883#AppAgentNodeProperties(M)-max-business-transactions ) The maximum value allowed for this property is 200.   Note: Changing this setting can affect the resource consumption of your deployment. Before you change this setting, verify that your application environment and Controller can handle any increased resource requirements.   This will help to discover the important BTs and move it to the main list ... View more

If you need 1:1 expert AppDynamics product advice, you can book a 1:1 meeting with one of our technical consultants. Set up half-hour meeting with our Call-a-Consultant service right on the calendy page.  Topics range from installation and configuration, to dashboarding, to best practices of APM, end user monitoring, and business performance monitoring products. NOTE: Call-a-Consultant is a service for AppD customers. ... View more

What are the steps to installing and validating a Java Agent?   Table of Contents How do I install the AppDynamics Java Agent? How do I validate that my deployed Java Agent is reporting?   How do I install the AppDynamics Java Agent? Download the latest Java Agent from download.appdynamics.com Unzip the folder to C:\AppDynamics\JavaAgent (<JavaAgent-Home>) Navigate to <JavaAgent-Home>\version xxx\confdirectory and edit controller-info.xml Input the following information a Controller hostname or IP address The same host you use to access the AppDynamics Controller's browser-based UI (for example  192.168.1.22 , or myhost , or myhost.xxx.com 😞 SaaS Controller Host: <controller-host>[xxx.saas.appdynamics.com]</controller-host> On-premises Controller Host: <controller-host> [On-premises Controller] </controller-host> OVERRIDE: You can override this configuration with the environment variable CONTROLLER_HOST_NAME , or the system property -Dappdynamics.controller.HostName   b  Controller HTTPS port The same port you use to access the AppDynamics Controller's browser-based UI: SaaS Controller Port:  <controller-port>[443]</controller-port> On-premises Controller Port: <controller-port>[On premises controller port]</controller-port>   DEPENDENCY: If <Controller-ssl-enabled>  (in row "C"  below) is set to “true” specify, the Controller's HTTPS port  (default is 8181). I f it is set to "false", specify the HTTP port (default is 8090) instead.   OVERRIDE: You can override with the environment variable:  CONTROLLER_CONTROLLER_PORT or the system property -Dappdynamics.controller.port   c Specify whether  to connect with SSL (HTTPS) or not The Agent only connects to the Controller using SSL when you enable this property. Otherwise, it connects using HTTP. If you set <Controller-ssl-enabled> to “true”, then set the controller-port property to the Controller's HTTPS  (see step “b”, above).  <controller-ssl-enabled>[set to true or false]</controller-ssl-enabled>   OVERRIDE: You can override with the environment variable:  CONTROLLER_CONTROLLER_SSL_ENABLED or the system property   -Dappdynamics.controller.ssl.enabled   d Application name The logical business application name that the JVM node belongs to, and NOT the deployment name (EAR, WAR, JAR) on the application server. <application-name></application-name>   For example, if monitoring a portal application or "Acme eCommerce", you could name a business application "Acme Portal". If a business application of that name doesn't exist, the Controller will create one.    OVERRIDE: You can override this setting with the environment variable  APPDYNAMICS_AGENT_APPLICATION_NAME   or the system property   -Dappdynamics.agent.accountAccessKey   e Tier name The logical business tier this node belongs to.  For example, a tier could be 'Acme frontend' or 'Acme Backend Service'. If your JVM/app server startup script contains a system property you want to use for the tiername (e.g., '-Dserver.tier'), you can use expressions like '${server.tier}_${some.property}.MyTier' to define the tier name.    OVERRIDE: You can override this setting with the environment variable  APPDYNAMICS_AGENT_TIER_NAME   or the system property   -Dappdynamics.agent.tierName   f Node name The name for this access node, which must be unique within the business application, e.g., 'weblogicinstance23', or 'hweb24'.  If your JVM/appserver startup script contains a system property you want to use for the node name (e.g., -Dserver.name ), you can refer to the system similarly (e.g., ${server.name} ). The value for server.name will be used as AppDynamics node name.   OVERRIDE: You can override this configuration with the environment variable APPDYNAMICS_AGENT_NODE_NAME or the system property  -Dappdynamics.agent.nodeName   g Account name If you’re running in single-tenant mode (the default), you don’t need to configure this value.   <account-name>xxx</account-name>   OVERRIDE: You can override this configuration with the environment variable  APPDYNAMICS_AGENT_ACCOUNT_NAME or the system property  -Dappdynamics.agent.applicationtName h The account access key <account-access-key>xxx</account-access-key> If 'use-encrypted-credentials' is set to true, use the encrypted account access key.   OVERRIDE: You can override this configuration with the environment variable APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY or with the system property  Dappdynamics.agent.accountAcccessKey   Attach the Java Agent to the JVM. Depending on the JVM framework and the Java Agent downloaded, you can follow the installation scripts in Agent Installation by Java Framework In general, the —javagaent argument is appended to the startup command for the JVM. The argument should indicate the location of the Java Agent JAR file: -javaagent:<agent_home>/javaagent.jar   How do I validate that your deployed Java Agent is reporting? To validate that the Machine Agent is reporting on the Controller, navigate to Settings, then AppDynamics Agents. Click the AppServer Agents tab. ... View more

What are the steps to installing and validating a Machine Agent?   Table of Contents How do I install the AppDynamics Machine Agent? How do I validate that my deployed Machine Agent is reporting?   How do I install the AppDynamics Machine Agent? Download the latest Machine Agent from download.appdynamics.com Unzip the folder on the server to be monitored Navigate to Machine Agent home folder > conf > controller-info.xml Input the following information Host name or IP address a Same host used to access AppDynamics browser-based UI <controller-host>xxx.saas.appdynamics.com/On-prem controller</controller-host> Can be overridden with the environment variable CONTROLLER_HOST_NAME or the system property ‘-Dappdynamics.controller.HostName ’ HTTPS port b Same port used to access AppDynamics browser-based UI <controller-port>443(for SaaS)/On prem controller port</controller-port> If <Controller-ssl-enabled> below (“c”), is set to “true” specify the HTTPS port of the Controller (default is 8181). If it is not, instead specify the HTTP port (default is 8090) Can be overridden with the environment variable  CONTROLLER_CONTROLLER_PORT or the system property ‘-Dappdynamics.controller.port’ Specify whether to use SSL (HTTPS) to connect c <controller-ssl-enabled>true(SaaS)/false</controller-ssl-enabled> If <Controller-ssl-enabled> , is set to “true” here, specify the HTTPS port of the Controller above (“b”) (default is 8181); if it is not set to true, instead specify the HTTP port (default is 8090). Can be overridden with the environment variable CONTROLLER_CONTROLLER_SSL_ENABLED or the system property '-Dappdynamics.controller.ssl.enabled' Account access key d The account access key is generated at installation. You can find it with the License information in the Controller Settings.  <account-access-key> xxxxxx</account-access-key> Can be overridden with the environment variable APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY or the system property  ‘-Dappdynamics.agent.accountAccessKey' Account name e If the AppDynamics Controller is running in multi-tenant mode, or if you’re using the AppDynamics SaaS Controller, you must specify the account name for this agent to authenticate with the controller: <account-name>xxxxx</account-name> If you’re running in single-tenant mode (the default), you don’t need to configure this value. Can be overridden with the environment variable APPDYNAMICS_AGENT_ACCOUNT_NAME or the system property ‘-Dappdynamics.agent.accountName' Server monitoring enabled/disabled f If this agent is licensed for server monitoring, set this flag to true to enable Server Monitoring expanded metrics. <sim-enabled>true(for server visibility)</sim-enabled> Can be overridden with the environment variable APPDYNAMICS_AGENT_SIM_ENABLED or the system property ‘-Dappdynamics.sim.enabled' .NET compatibility mode enabled/disabled g Optional  If there is a .NET Agent on the same server, enable .NET compatibility <dotnet-compatibility-mode>true</dotnet-compatibility-mode> Navigate to <MachineAgent-Home>  and run script InstallService.vbs . This will configure the Machine Agent as a service as well as start it.   How do I validate that your deployed Machine Agent is reporting? To validate that the Machine Agent is reporting on the Controller, navigate to Settings, then AppDynamics Agents. Click the Machine Agent tab. ... View more

What are the steps to installing and validating a .NET Agent?   Table of Contents Install the AppDynamics .NET Agent Validate that your deployed .NET Agent is reporting   How do I install the AppDynamics .NET Agent? Download the latest .NET agent from download.appdynamics.com Launch the .NET Agent MSI Agree to the End User Agreement and follow the Wizard prompts to set up the .NET Agent. The agent will be installed as a Windows Service Launch the AppDynamics Configuration Utility Fill in your Controller credentials. Then, test the Controller connection Server (Name/IP) example.saas.appdynamics.com (or the IP address of an on-premises Controller) Port Number SaaS: 443 On premises: generally 8090, depending on your configuration Account Name See your account name on Controller Settings > Licenses > Account Access Key See your license on Controller Settings > Licenses > Account Enable SSL For a SaaS environment, check to enable TSL 1/2 For a SaaS environment, check to enable .NET Agent Configuration: Controller configuration credentials Follow through the Wizard’s remaining steps to configure the IIS applications you want to monitor, and complete the tier assignment Finish the Wizard by applying the configuration. Then restart the IIS.   How do I validate that the new .NET Agent is reporting? Sign in to the Controller UI to validate that the Agent is reporting: Click Applications in the top navigation bar Select Tiers & Nodes in the left navigation bar On the Tiers & Nodes panel, the tier name you’re validating should appear according to your configuration settings Check the Tiers & Nodes panel for the name of the tier you are validating   Note: The .NET Agent initially reports under the Machine Agent tier. Once the instrumented application receives load, the agent starts reporting under the specified Tier Name. ... View more

Preparatory steps to getting started with AppDynamics SaaS Controller   Table of Contents How do I access my Controller for the first time? How do I set up my AppDynamics Master Account? Reset your Master Account credentials Set up your company’s users View license consumption What are the pre-requisites for setting up my network ports for Controller connection?   How do I access AppDynamics for the first time? Your company’s primary contact will receive a welcome email from the SaaS Operations or Sales team. It will include your AppDynamics Controller URL.   Your primary contact will be able to follow the link, and create new user accounts for the Controller, giving access to others in your organization.   How do I set up my AppDynamics Master Account? The same email includes the instructions your primary contact will need to set up your AppDynamics Controller. The areas are: Resetting your master account credentials Setting up your company’s users Viewing license consumption   Reset your Master account credentials The following instructions are specific to SaaS accounts: Look for the Master account name in the welcome email and make not of it Navigate to the Controller URL, also provided in that email Click on Forgot Password Enter the Master account name in both the username and account name fields, then click the Reset Password button   Controller URL's "Forgot Password" dialog, where you enter your Master Account name in the Account and Username fields Through the Reset Password process, the SaaS url link will be sent to the primary contact’s email address.    After the primary contact resets the password reset, you will be able to add AppDynamics users. go to your Controller URL and navigate to Settings -> Administration and Add AppDynamics users. Note : Looking for how to reset passwords for individual accounts that have been created in the AppDynamics controller? See How do I reset my individual password for the Controller   Set up your company’s users Your Master Account is granted the status of Account Owner (Default). This role allows access to all other roles on the Controller.    To learn more about Controller roles and their privileges, see Roles and Permissions .   View license consumption? To check your license consumption: Click the gear icon on the top right navigation bar Click License See your license consumption on the Account Usage tab Under the gear icon, click "License" . Your license consumption is found under Account Usage.   What are the prerequisites for setting up my network ports for Controller connection? In order to set up your Controller connection, the following ports need to be open: Application servers Application servers may need to find APM Agents, application-related agents, and DB agents. Both the APM agents and the DB agents need open ports to send out the data to the SaaS AppDynamics controller. Open Outbound Ports 443 from all application servers/database to AppDynamics controller, allowing the agents to send data out Javascript beacons Our Javascript Agent (adrum.js) sends the beacons as POST requests to these EUM server endpoints which reside on AppDynamics cloud. So, if on an intranet, your networks need connectivity to reach the following end points: EUM Collector:  https://col.eum-appdynamics.com EUM API:  https://api.eum-appdynamics.com Analytics Server Access The analytics server needs outbound network access from the applications server to the analytics endpoint:  https://analytics.api.appdynamics.com/     Additional Resources How do I check my license usage at the account level? What are some best practices for license management? Where do I find my subscriptions and license details? ... View more