Connecting Applications to AOM

Procedure

1. Log in to the AOM 2.0 console.
2. In the navigation pane on the left, choose Access > Access Center. (To switch from the new access center to the old one, click Back to Old Version in the upper right corner.)
3. In the Application panel on the right, click the target card and perform the operations listed in the following table if needed.

   Table 1 Connecting applications to AOM

   Card

   Related Operation

   Java

   On the Connect Application page, ingest trace metrics related to Java applications. AOM supports quick connection to Agents to monitor Java applications. You can also install Agents for the Java applications deployed in CCE containers for monitoring. For details, see Monitoring Java Applications Through Quick Connection to Agents and Monitoring Java Applications Deployed in CCE Containers by Installing Agents.

Monitoring Java Applications Through Quick Connection to Agents

AOM allows you to monitor Java applications through quick connection to Agents. Java supports enhanced Agents.

• Prerequisites

  The network between your host and APM is connected.

  You can run the Telnet command to check the network. For example, if you select region CN-Hong Kong and set Access Mode 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.

• Procedure
  1. Log in to the AOM 2.0 console.
  2. In the navigation pane, choose Access > Access Center.
  3. In the Application panel, click the Java card. (In the new access center, click the Java Component card under the Components panel.)
  4. In the Basic Info area, select a region and an application.
     If no applications meet your requirements, create one. For details, see Table 2.

     Figure 1 Basic information
     

     Table 2 Parameters for adding an application

     Parameter	Description
     Application Name	Name of an application, which cannot be empty. Enter 1 to 128 characters and start with a letter. Only digits, letters, underscores (_), and hyphens (-) are allowed.
     Application Alias	Application alias. The alias takes precedence over the application name to display. Enter 1 to 128 characters. Only digits, letters, underscores (_), hyphens (-), brackets, and periods (.) are allowed.
     Enterprise Project	Select an enterprise project from the drop-down list. This parameter is displayed only when you use the enterprise edition.
     Description	Description of the application. Enter up to 1,000 characters.

  5. (Default) Set Access Mode to Enhanced Agent.
  6. Set Data Access to VM access and ingest the data as prompted.
     Figure 2 VM access
     
     1. Use a remote login tool, such as PuTTY, to log in to the Linux host where the Agent is to be installed and run the copied command as the root user to download and install JavaAgent.

        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 
        • APM_AK/APM_SK: AK and SK for installing JavaAgent. For details about how to obtain an AK and SK, see Access Keys. Directly copy the command for installing JavaAgent. Delete {} when entering APM_AK and APM_SK.
        • master.address: the access address of an APM Agent. For more information, see Access Addresses.
        • Supports dynamic configuration of AK/SK in the JavaAgent installation command and master.address: Assign values to environment variables APM_MASTER_ADDRESS, APM_ACCESS_KEY (apm-ak), and APM_SECRET_KEY (apm-sk).
     2. After installing the JavaAgent, add JVM parameters to the startup script of your application and then restart it.

        Table 3 JVM parameters

        Parameter	Description	Mandatory
        Agent Installation Path	Path for installing the Agent.	Yes
        appName	Component name, which must start with a character. Each component name must be unique under an application. A component can contain multiple environments. 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 share the same tag. This parameter can be left blank.	No
        business	Name of an application (a global concept). Create an application before specifying this parameter. If this parameter is left blank, the default application (which is automatically created when you enable APM) will be used.	No
        subBusiness	Name of a sub-application (a global concept). It is a folder under the application. This parameter can be left blank. If it is left blank, resources will be mounted to the root application. Up to three layers of sub-applications are supported. For example, for a/b/c, each represents one layer.	No
        User Application	Name of a user application.	Yes

Monitoring Java Applications Deployed in CCE Containers by Installing Agents

AOM allows you to install APM Agents for Java applications deployed in CCE containers for monitoring. It enables precise problem analysis and locating, accelerate troubleshooting.

• Prerequisites
  • The network between your host and APM is connected.

    You can run the Telnet command to check the network. For example, if you select region CN-Hong Kong and set Access Mode 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.

  • The endpoint of the target region has been obtained. For details, see Regions and Endpoints.
  • The AK/SK required for installing JavaAgent has been obtained. To do so, go to the AOM 2.0 console and choose APM Settings > Access Keys in the navigation pane.
• Instructions

  You can configure performance management for Java workloads when and after the workloads are created. Agents can only be installed for Java applications deployed in CCE containers. For details, see Configuring APM. You are advised to install self-developed probes for applications deployed in CCE containers.

  Table 4 describes the parameters.

  Table 4 Parameters for configuring APM

  Parameter	Description
  Probe	Select a target probe. Options: Disable/APM 2.0.
  Probe Version	Version of the probe. You are advised to select a probe version based on the CPU architecture of the node where the workload is located.
  Probe Upgrade Policy	Policy for the probe upgrade. The default value is Auto upgrade upon restart. Auto upgrade upon restart: The system downloads the probe image each time the pod is restarted. Manual upgrade upon restart: If a local image is available, it will be used. If no local image is available, the system downloads the probe image.
  APM Environment	Enter an APM environment name. This parameter is optional.
  APM App	Select an existing APM application.
  Sub-app	Enter an APM sub-application. This parameter is optional.
  Access Key	The key of APM is automatically obtained. For details, see Prerequisites.