Help Center> Cloud Container Engine> User Guide> Old Console> Workloads> Configuring a Container> Configuring APM Settings for Performance Bottleneck Analysis
View PDF

Configuring APM Settings for Performance Bottleneck Analysis

Scenario

Currently, tracing, topology, and other O&M tools are supported for Java workloads. If you want to monitor the status of a Java workload, select Java probe in the APM Settings area of the Configure Advanced Settings page during workload creation and enter a monitoring group name.

You can configure Java workload monitoring when and after a workload is created.

  • You need to connect your Java application on CCE to Application Performance Management (APM) through the Pinpoint probe. For details, see Connecting a HUAWEI CLOUD Containerized Application to APM.
  • If you have not enabled the Application Performance Management (APM) service, click Buy Package, select the number of application instances as prompted, and click Pay Now. After confirming the order, click Pay Now again to submit the order.

Procedure

  1. Log in to the CCE console. In the navigation pane, choose Workloads > Deployments or Workloads > StatefulSets, and click Create Deployment or Create StatefulSet.
  2. In the APM Settings area on the Configure Advanced Settings page, select Java probe. The Application Performance Management (APM) service will be enabled and a probe will be installed on the node.

    Currently, the APM1.0 and APM2.0 probes are supported. You are advised to select the APM2.0 probe.

    The probe provides call chains, topology, SQL analysis, and stack tracing for Java workloads. For running the probe, a small amount of CPU and memory resources will be consumed.

  3. Set probe-related parameters.

    Figure 1 Configuring APM settings
    • Monitoring group (only for APM1.0): Enter the monitoring group name, for example, testapp. If one or more monitoring groups are available, you can select one from the drop-down list.
    • Probe Version: Select the probe version.
    • 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.
    • APM Environment (only for APM2.0): environment created in APM.
    • APM Service (only for APM2.0): Select the service and subservice created in APM.
    • Access Key (only for APM2.0): The access key is automatically obtained.

  4. Three minutes after the application is started, its data will be displayed on the APM console. You can log in to the APM console and optimize application performance through topology and tracing. For details, see APM User Guide.

Parent topic: Configuring a Container