Help Center> ServiceStage> User Guide> Component Management> Component Advanced Setting> Configuring Application Performance Management
Updated on 2024-05-28 GMT+08:00
View PDF

Configuring Application Performance Management

Performance management helps you quickly locate problems and identify performance bottlenecks to improve your experience. Selecting Java probe will start performance management and install Java probes on the nodes deployed with performance management, 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.

ServiceStage allows you to configure performance management during component deployment (using CCE).

Precautions

  • This function can be enabled only when APM of the corresponding version is deployed and enabled in the environment.
  • JDK 8, 11, and 17 are supported.
  • Supported Tomcat versions: 8.x. 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.

Procedure

  1. Choose Advanced Settings > O&M Monitoring.
  2. On the Performance Management tab, configure performance management as follows:

    Select Java probe and set probe parameters.
    • If the probe type is APM 1.0, select a probe version from the drop-down list.
    • If the probe type is APM 2.0, set the following parameters:
      • 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.
      • Probe Version: Select a probe version from the drop-down list.

        To use the probe of the latest version, select latest.

      • Upgrade Policy: The following upgrade policies are supported. By default, Automatic upgrade upon restart is used.
        • 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.
      • Access Key: The access key is automatically obtained. If the access key cannot be automatically obtained, manually enter it.