Connecting Agents

Prerequisites

The network between your host and APM is normal.

You can run the Telnet command to check the network. For example, if you select region CN-Hong Kong and set Code Source to Enhanced Agent, log in to the host where the application is deployed and run the telnet 100.125.6.106:41333 command to check the network connectivity. For details about access addresses in other regions, see Access Addresses.

Java supports enhanced Agents.

Procedure

Log in to the management console.
Click on the left and choose Application > Application Performance Management.
In the navigation pane, choose Application Monitoring > Applications.
On the displayed page, click Connect Application.

Figure 1 Connecting an application
Select a region and application.

Figure 2 Basic information
Select Enhanced Agent for Access Mode.
Select Java for Backend Language.

Figure 3 Access mode

Select an access mode based on the application type and access data by following the instructions.

Figure 4 Data access
Click to enlarge

**Table 1** Parameter description
Parameter	Description	Mandatory
APM_AK APM_SK	AK and SK for installing JavaAgent. To obtain APM_AK and APM_SK, see Access Keys. CAUTION: When you copy the command to install JavaAgent, delete {} when setting APM_AK and APM_SK. Example: curl -k https://javaagent.**/apm_agent_install2.sh -o apm_agent_install.sh && bash apm_agent_install.sh -ak -sk * -masteraddress https://** -obsaddress https://javaagent.*.com -version latest; history -cw; history -r	Yes
Probe Installation Path	Path for installing the Agent.	Yes
appName	Component name, which must start with a letter. A component can contain multiple environments. The names of components under an application must be unique. If there are duplicate names, use instanceName to distinguish them.	Yes
env	Name of an environment where an application is deployed. A program can be deployed in different environments (such as the test or live network environment). Each environment is deployed in one region and has a unique region attribute. If this parameter is blank, the default environment will be used.	No
envTag	Environment tag for filtering environments. Different environments may have the same tag. This parameter can be left blank.	No
business	Name of an application that already exists (a global concept). If this parameter is left blank, the automatically created application will be used.	No
subBusiness	Name of a sub-application (a global concept), which is similar to a folder. If it is left blank, resources will be mounted to the root application. There can be up to three layers of sub-applications. For example, for a/b/c, a, b, and c respectively represents a layer.	No
User Application	Name of a user application.	Yes

Dynamically Configuring master.address and AK/SK

APM supports dynamic configuration of the master.address and AK/SK.

You can set the APM_MASTER_ADDRESS, APM_ACCESS_KEY (apm-ak), and APM_SECRET_KEY (apm-sk) environment variables. For details about how to obtain the AK/SK, see Manually Installing Agents for Java Applications. For details about how to obtain the master.address, see Access Addresses.

If you set the AK/SK and master.address in both the JavaAgent configuration file and environment variables, your environment variable settings will take precedence.
Agents later than 2.3.19 support dynamic configuration of master.address and AK/SK.

Parent topic: Monitoring Java Applications

Previous topic: Monitoring Java Applications

Next topic: Manually Installing Agents for Java Applications