Configuring Performance Management of a Container-Deployed Component

Performance management helps you quickly locate problems and identify performance bottlenecks to improve your experience. Selecting Java probe will start APM and install Java probes on the nodes deployed with APM, which consumes a small amount of resources. Java probes use the bytecode enhancement technology to trace Java application calls and generate topology and call chain data.

You can configure performance management of container-deployed components when configuring Advanced Settings.

Restrictions

This function can be enabled only when APM of the corresponding version is deployed and enabled in the environment.
JDK 8, 11, 17, and 21 are supported.
Tomcat 8.x and 9.x are supported. For details, see Usage Restrictions.
Performance management can be configured for Java applications (technology stack type being Java, Tomcat, or Java-based Docker) deployed using CCE.

Configuring Application Performance Management

Choose Advanced Settings > Performance Management.

Select Java probe and set probe parameters based on your probe type by referring to the following table.

Probe Type	Description
APM 1.0	Select a probe version from the drop-down list.
APM 2.0	Set Application. Select the application that has the same name as the application where the application component is located from the drop-down list. If the application does not exist, click Create Application to create it. After the application is created, you can log in to the APM console and view the new application in the application list. Set Probe Version. Select a probe version from the drop-down list. NOTE: You can select a probe version based on the CPU architecture of the master node in the CCE cluster where the component is deployed. For example, if the CPU architecture is x86_64, select latest-x86_64. Set Upgrade Policy. Select a probe upgrade policy. By default, Automatic upgrade upon restart is selected. Automatic upgrade upon restart: The system downloads the probe image each time the pod is restarted. Manual upgrade: This policy means that if a local image is available, the local image will be used. The system downloads the probe image only when a local image is unavailable. Set Access Key. The access key is automatically obtained. If the access key cannot be automatically obtained, manually enter it.

Probe Type

Description

APM 1.0

Select a probe version from the drop-down list.

APM 2.0

Set Application.
- Select the application that has the same name as the application where the application component is located from the drop-down list.
- If the application does not exist, click Create Application to create it. After the application is created, you can log in to the APM console and view the new application in the application list.
Set Probe Version.
Select a probe version from the drop-down list.

NOTE:

You can select a probe version based on the CPU architecture of the master node in the CCE cluster where the component is deployed. For example, if the CPU architecture is x86_64, select latest-x86_64.
Set Upgrade Policy.
Select a probe upgrade policy. By default, Automatic upgrade upon restart is selected.
- Automatic upgrade upon restart: The system downloads the probe image each time the pod is restarted.
- Manual upgrade: This policy means that if a local image is available, the local image will be used. The system downloads the probe image only when a local image is unavailable.
Set Access Key.
The access key is automatically obtained. If the access key cannot be automatically obtained, manually enter it.