Configuring Component Settings for Performance Monitoring

Custom Settings

You can configure log association, Profiler, component/infrastructure association analysis, full sampling, and database monitoring settings.

1. Log in to the APM console.
2. Click on the left and choose Management & Governance > Application Performance Management.
3. In the navigation pane, choose Performance Monitoring > Components.
4. In the filter bar on the left, select a region and application to filter components.

   You can also specify an application and component in the search box to filter the target component.

5. Click a component name in the Component column. The component details page is displayed.
6. Click the Component Settings tab. On the displayed page, perform the following operations:
   • Log Association Settings:

     You can associate trace IDs with logs in LTS. If a fault occurs, you can quickly find out the logs based on the associated trace IDs for troubleshooting.

     1. In the Log Association Settings area on the Custom Settings page, enable or disable Associate Log with Trace ID.
        • If this option is enabled, trace IDs will be automatically generated in service logs.
        • If this option is disabled, the log association settings below this option will not take effect.
        • Only Log4j, Log4j2, and Logback log components support the association.
        • Log association settings can be configured for Java components only.
     2. In the Log Association Settings area, set parameters by referring to the following table. After the configuration is complete, the Save and Clone to Other Component buttons turn black.

        Table 1 Parameters for log association settings

        Parameter	Description
        Project	Select a project from the drop-down list.
        Log Group	Select a log group. A log group is a group of log streams which share the same log retention settings. Up to 100 log groups can be created for a single account. For details about how to create a log group, see Creating a Log Group.
        Log Stream	Select a log stream. A log stream is the basic unit for reading and writing logs. You can put different types of logs into different streams to ease management. For details about how to create a log stream, see Creating a Log Stream.

     3. Click Save.
     4. In the displayed dialog box, click Confirm.
   • Profiler Settings
     1. In the Profiler Settings area on the Custom Settings page, set parameters by referring to the following table.
        • Profiler settings can be configured for Java components only.
        • To use Profiler for performance analysis, install an Agent version that supports Profiler.

        Table 2 Parameters for Profiler settings

        Parameter	Description
        Enable/Disable Profiler	Enable or disable Profiler: Enable: APM performs Profiler analysis. APM will then diagnose applications to solve performance bottlenecks caused by high CPU/memory usage or latency. Disable: APM does not perform Profiler analysis. This option is disabled () by default. When Enable/Disable Profiler is disabled, all the options below are disabled.
        CPU	Enable or disable CPU: Enable: APM collects CPU flame graph information during application running. Disable: APM does not collect CPU flame graph information during application running. This option is disabled () by default.
        Memory	Enable or disable Memory. Enable: APM collects heap memory flame graph information during application running. Live Object Memory: heap memory that has been allocated but has not been reclaimed. It is used in the memory leakage scenario. Ensure that JDK17 is used. Allocated Memory: allocated heap memory (including the memory that has been reclaimed and that has not been reclaimed). It can be used in the frequent Garbage Collection (GC) scenario. Disable: APM does not collect heap memory flame graph information during application running. This option is disabled () by default.
        Latency	Enable or disable Latency. Enable: APM collects latency flame graph information during application running. Disable: APM does not collect latency flame graph information during application running. This option is disabled () by default.
        Effective Scope	Set the effective scope: Component: This setting takes effect in a component. Profiler data is generated for all instances associated with the component. The default effective scope is Component. Instance: This setting takes effect in instances. Profiler data is generated for the selected instances only. If the effective scope is set to Instance, you need to select instances. Click Selecting an instance under Instance. Select one or more instances and click Confirm.

     2. Click Save.
     3. In the displayed dialog box, click Confirm.
   • Component/Infrastructure Association Analysis
     1. In the Component/Infrastructure Association Analysis area on the Custom Settings page, select a scenario and a Prometheus instance.

        After components are associated with Prometheus instances, you can monitor containers or VMs on the component details page.

        Figure 1 Component/Infrastructure association analysis
        
        1. Container: Container middleware and container metrics are stored in the Prometheus instance for CCE.

           If association analysis is required, create a Prometheus instance for CCE in AOM and then connect the target cluster for monitoring on the Prometheus instance details page.

        2. VM: Metrics of resources such as VMs and self-built middleware are stored in the Prometheus instance for ECS.

           To perform association analysis, create a Prometheus instance for ECS in AOM and then install the Node Exporter or self-built middleware Exporter in AOM's access center.

     2. Click Save.
   • Full Sampling Settings
     • To enable full sampling, go to JavaAgent Updates and select a proper version. A higher sampling ratio means more resources consumed. Ensure that your resources are sufficient before setting a sampling ratio.
     • When the sampling ratio is set to 100%, the CPU usage is about 5%, 10%, or 20% higher than that of intelligent sampling in the case of 500 TPS, 1,000 TPS, or 2,000 TPS.
     • Full sampling can be configured for Java components only.
     1. In the Full Sampling Settings area on the Custom Settings page, select a sampling policy.
        • Intelligent: Intelligent algorithms are used for sampling. For details, see Intelligent Sampling Algorithm.
        • Global: Set a sampling ratio for all traces.

          Table 3 Global sampling parameters

          Sampling Ratio Name	Default Value	Range	Description
          Maximum sampling threshold per second	100	0–200	Default value: 100 This parameter is set to protect services from being affected by sampling in large traffic scenarios. If you set a value greater than the default value, additional system resources will be consumed. Exercise caution. Ensure that Agent 2.5.5 or later is installed.
          Global Sampling Ratio	100%	0%–100%	Set a sampling ratio for all traces.

        • Custom: Set a custom sampling ratio as required.

          Table 4 Parameters of custom sampling

          Sampling Ratio Name	Default Value	Range	Description
          Maximum sampling threshold per second	100	0–200	This parameter is set to protect services from being affected by sampling in large traffic scenarios. If you set a value greater than the default value, additional system resources will be consumed. Exercise caution. Ensure that Agent 2.5.5 or later is installed.
          Successful Request Sampling Ratio	100%	0%–100%	Set a success request sampling ratio. Successful requests do not return the defined error codes.
          URL Sampling Ratio	100%	0%–100%	The URL sampling ratio takes effect only for successful requests. Click Add and set the following parameters: URL: URL path. Example: /apm2/health/v1/health-check. Sampling Ratio: 0%–100%. To delete the configured URL sampling ratio, click Delete. The URL refers to the URL with RT Threshold defined in URL Configuration of the URL monitoring item. For details about the configuration, see Configuring the URL Monitoring Item.
          Error Request Sampling Ratio	100%	0%–100%	Set an error request sampling ratio. An error request refers to the request that returns the Error Code defined in the URL monitoring item. For details about the configuration, see Configuring the URL Monitoring Item.
          Slow Request Sampling Ratio	100%	0%–100%	Set a slow request sampling ratio. A slow request refers to the request whose response time is greater than Slow Request Threshold defined in the URL monitoring item. For details about the configuration, see Configuring the URL Monitoring Item.

     2. Click Save. The full sampling settings take about 10 minutes to be effective.
   • Database Monitoring Settings
     • You can define a slow SQL threshold. Requests that exceed this threshold are regarded as slow and will be displayed on the URL page and in monitoring reports.
       1. On the Custom Settings page, set Slow SQL Threshold in the Database Monitoring Settings area.
          • Value range: [100, 20000]. The default value is the same as the SQL threshold configured in the system.

7. Click Save. You can click Clone to Other Component in each configuration area to clone the configuration to other components. You can also click Clone to Other Component in the lower right corner of the page to clone entire configurations to other components in batches.

Configuring an Agent

1. Log in to the APM console.
2. Click on the left and choose Management & Governance > Application Performance Management.
3. In the navigation pane, choose Performance Monitoring > Components.
4. In the filter bar on the left, select a region and application to filter components.

   You can also specify an application and component in the search box to filter the target component.

5. Click a component name in the Component column. The component details page is displayed.
6. Click the Component Settings tab and go to the Agent Settings page. Then you can view host information and perform operations such as enabling or disabling Agents. For details, see Managing Performance Monitoring Agents.

Configuring a Monitoring Item

1. Log in to the APM console.
2. Click on the left and choose Management & Governance > Application Performance Management.

1. In the navigation pane, choose Performance Monitoring > Components.
2. In the filter bar on the left, select a region and application to filter components.

   You can also specify an application and component in the search box to filter the target component.

3. Click a component name in the Component column. The component details page is displayed.
4. Click the Component Settings tab and go to the Monitoring Item page. Then you can view parameters such as Monitoring Item, Monitoring Item Name, and Collection Interval, and perform the following operations:

   Table 5 Operations on monitoring items

   Operation	Description
   Enabling or disabling a monitoring item	Click the button in the Enable/Disable Monitoring Item column. A monitoring item is enabled () by default.
   Editing a monitoring item	Click Modify in the Operation column to modify the monitoring item configuration. For details, see Configuring a Monitoring Item.
   Refreshing monitoring items	Click in the upper right corner of the monitoring item list to obtain the latest information about all monitoring items in real time.