On this page:
Before an App Agent can upload data to the Controller, you must configure its connection to the Controller. Agents connect to the Controller through the same port as the browser connection for the UI, on port 8090 by default.
You can configure the agent to connection through a web proxy for the Controller. It can also connect to the Controller using an SSL connection. See Security for information on using SSL.
Connect the Agent to the Controller
The connection between the Controller and agent is generally a one-way connection. The agent initiates the connection to the Controller. Thus, the settings you configure to allow for the connection are in the agent. If you downloaded the agent through the Agent Download Wizard in the Controller, the properties are already configured for you.
Configure these properties:
- Controller Host
- Controller Port
If you are using a SaaS or on-premise multi-tenant Controller, also configure:
- Account Name for SaaS
- Account Access Key or Password for SaaS
If you are a SaaS user, the account name and access key settings you use should be in your welcome email from AppDynamics.
The following section lists the locations and options for configuring the settings for each type of agent.
Configuration File Locations for App Agents
The way you configure the Controller connection varies slightly among the different types of agents, as described here.
Configure Controller connectivity for the Java Agent in either of the following places:
- In the controller-info.xml configuration file
- In system properties (-D options) passed in the JVM startup script or command line
- In environment variables
The system properties override the settings in the controller-info.xml.
The NET Agent includes the AppDynamics Agent Configuration utility to assist configuration. See Configure the .NET Agent.
For more information, see:
Configure Controller connectivity for the App Agent for PHP in the php.ini file.
When you install the PHP agent, provide the relevant Controller connection information. The install script writes the configuration to php.ini.
For more information, see:
- Install the PHP Agent using a Shell Script
- Install the PHP Agent using RPM
- Controller Information in the PHP Configuration Files
All the Controller information is in the require statement that you add to the code when you instrument the application.
Configure Controller connectivity for standalone machine agents in <machine_agent_home>/conf/controller-info.xml.
Securing the Connection
The on-premise Controller is installed with an active secure port by default. App Agents can use the secure port to connect to the Controller.
The certificate used for the connection out-of-the-box is a self-signed certificate. The .NET agents cannot connect on a secure port that uses a self-signed certificate, so you will need to apply your own certificate to the port. App Agents connecting to an AppDynamics SaaS Controller also must use an HTTPS connection.
The default secure listening port for the AppDynamics Controller are:
- For on-premise Controllers, port 8181
- For SaaS Controllers, port 443
To implement SSL for the Controller-agent connection:
- Set the application server primary port to the SSL port, by default 8181. See Controller Port Settings.
- Install a trusted certificate, see Controller SSL and Certificates.
- Configure your agents for SSL. See the following sections, App Agent Security and Machine Agent Security, for more information.
The SaaS Controller is already configured for SSL, so to enable your environment for SSL you only need to do the following:
- Configure your agents for SSL by enabling SSL and setting the port connection for the SaaS Controller to 443. See the following sections, App Agent Security and Machine Agent Security, for more information.
App Agent Security
To configure your agents for SSL, set these SSL-related properties:
- Set controller-ssl-enabled to true.
- Set the controller-port to the correct value for either on-premise or SaaS Controller.
In multi-tenant and SaaS environments, App Agents authenticate themselves to the Controller using the required account name and account access key values set in the connection properties configuration file.
Standalone Machine Agent Security
For information on the security settings related to the Standalone Machine Agent connection to the Controller, see Standalone Machine Agent Configuration Properties.
Verify the Connection
Follow these instructions to verify that the Java or .NET App Agent is reporting to the AppDynamics Controller.
Access the AppDynamics Controller UI:
For an on-premise Controller, open a browser at:
For a SaaS Controller, open a browser at the URL provided to you by AppDynamics.
- Provide user credentials:
- For on-premise Controller installations, provide the credentials for the "admin" user as configured during AppDynamics Controller installation.
- For the SaaS Controller Service, use the credentials provided to you by AppDynamics.
- In the left navigation panel, click on an application.
- Click Servers -> App Servers -> <TierName>.
The Tier Dashboard for the selected tier appears.
- Click the Nodes tab.
When an App Agent is reporting to the Controller, the App Agent Status column shows a green up arrow icon.
If the agent is not reporting to the Controller, see troubleshooting information:
If traffic is not being properly correlated between tiers, make sure that any network components (such as load balancers or routers) that sit between monitored nodes need to preserve the AppDynamics correlation header from HTTP traffic.