Updated on 2026-02-25 GMT+08:00

Monitoring Component Performance Metrics

The component details page displays components' monitoring items, including Overview, Topology, Profiler Performance Analysis, Debugging Diagnosis, URL, Info, Exceptions, External Calls, Communication Protocols, Databases, Cache, Web Containers, Message Queues, RPCs, Logs, Infrastructure, Tracing, and Component Settings.

Procedure

  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 an application.

    • In the search box, specify an application and component to filter data.
    • Click in the upper right corner of the list and select the columns to display.
    Table 1 Component metrics

    Metric

    Description

    Component

    Component name.

    Language

    Programming language of the component.

    Environment

    Environment where the component is located.

    Requests/s

    Number of requests per second of the component.

    Avg. RT

    Average response time in a collection period.

    Error Rate

    Error rate of the component = Number of abnormal URL calls of the component/Total number of URL calls of the component

    Alarms

    Severity of the alarms generated by the component and the number of alarms.

    The alarm severity can be major or minor.

    Application

    Application where the component is located.

  5. Click a component name in the Component column. The component details page is displayed.
  6. Click the name of a monitoring item. The corresponding monitoring item page is displayed. By default, the Overview page is displayed. For details about each monitoring item of the component, see Table 2.

    Table 2 Monitoring items of a component

    Module

    Description

    Overview

    The Overview page summarizes the performance monitoring data of component instances and displays Metric Overview, Performance Analysis, Resource Usage, and Top 5 APIs of the component in a specified period (max.: 30 days).

    For details, see Viewing the Component Overview.

    Topology

    The topology displays the call relationships between services within a period. The statistics can be collected from the caller or the callee. You can also view the trend.

    For details, see Viewing the Call Relationships Between Components in the Topology.

    URL

    This type of monitoring item monitors the calls of the current application by external services. It includes URL, Dubbo server, CSE server, CSEProvider cluster, and FunctionGraph monitoring. This type of monitoring item reflects the actual external status of the entire service. For example, if the average response time of a URL is long, it means that external users take a long time to query data.

    For details, see Viewing the URL Monitoring Item of a Component.

    Info

    This type of monitoring item monitors JVMInfo, JVMMonitor, GC, threads, and JavaMethod.

    For details, see Viewing the Info Monitoring Item of a Component.

    Exceptions

    This type of monitoring item monitors application exception logs. Take the monitoring of Java exception logs as an example. Once you use the log system to print logs, they will be collected by APM. The types of exceptions to be collected vary depending on the collector type.

    For details, see Viewing the Exception Monitoring Item of a Component.

    External Calls

    This type of monitoring item monitors the calls of external services by the current application. It includes CSEConsumer, ApacheHttpClient, ApacheHttpAsyncClient, DubboConsumer, and HttpClient.

    For details, see Viewing the External Call Monitoring Item of a Component.

    Communication Protocols

    This type of monitoring item monitors communication protocols, including the WebSocket protocol.

    For details, see Viewing the Communication Protocol Monitoring Item of a Component.

    Databases

    This type of monitoring item monitors database access. The databases that can be monitored include the C3P0, Cassandra, ClickHouse, DBCP, Druid, EsRestClient, GaussDB, Hikari, Jetcd, ObsClient, MySQL, PostgreSQL, Oracle, HBase, and MongoDB. APM collects statement execution details to help you locate performance problems in code.

    For details, see Viewing the Database Monitoring Item of a Component.

    Web Containers

    This type of monitoring item monitors web containers, including Tomcat.

    For details, see Viewing the Web Container Monitoring Item of a Component.

    Message Queues

    This type of monitoring item monitors message queues, including KafkaProducer.

    For details, see Viewing the Message Queue Monitoring Item of a Component.

    RPCs

    This type of monitoring item monitors remote procedure calls, including GRPCServer.

    For details, see Viewing the RPC Monitoring Item of a Component.

    Logs

    You can enter a keyword and specify a time range to search for logs. For details, see Viewing the Log Monitoring Item of a Component.

    Infrastructure

    Different graphs (such as line graphs and digit graphs) can be displayed on one dashboard, so you can view monitoring data comprehensively.

    For details, see Viewing the Infrastructure of a Component.

    Tracing

    When the calls between enterprise microservices are complex, APM Agents sample some requests, and intercept corresponding requests and subsequent call information. For example, in the scenario where service A calls service B and then calls service C, after service A receives a request, APM determines whether to trace the request based on the intelligent sampling algorithm.

    For details, see Viewing the Traces of a Component.

    Component Settings

    Component settings include log association, Profiler, component/infrastructure association analysis, full sampling, and database monitoring settings. For details, see Configuring Component Settings for Performance Monitoring.