edit-icon download-icon

Application monitoring overview

Last Updated: Nov 16, 2018

Application monitoring accurately reflects the real-time traffic and history information of an application, allowing you to monitor application health and quickly discover and locate problems.


  • TraceId: Corresponds to a request. It is globally unique and transmitted between systems.

    • IP Addresses: Indicates the IP address (in hexadecimal format) of the ECS instance that creates the TraceId.

    • Creation Time: Indicates the time for link creation.

    • Order: It is used for link sampling.

    • Flag Bit: (Optional) It is used for debugging and marking.

    • Process ID: (Optional) It is used for single-host multi-process applications.

  • RpcId: Calls and flags the log track order and nesting relationship. It is transmitted between systems.

  • Service Dimension: Service data is monitored in application and service dimensions. Data in the application dimension is aggregated by application, while data in the service dimension is aggregated by custom service. For example, you have an application A that provides services a, b, and c.

  • Drill Down: Views metrics of upstream (downstream) applications associated with the target metric.

Types of metric data

Tabs of different data types are available on the Service Monitoring page, allowing pertinent monitoring.

  • Provided RPC Service: Displays the RPC services (including the HSF and other custom services) provided by an application as the server.
  • RPC Call Source: Displays records of the following applications calling the RPC service provided by the current application.
  • RPC Call Dependency: Displays records of the current application calling RPC services (including HSF and other custom services) provided by other applications.

Types of monitoring reports

  • Mix of Graph and Table (Default): Displays data in “table + graph” form, including monitoring target, time, QPS, response time, server response time, errors, and results. By default, the graph shows data for the last hour, and the table shows data for the last five minutes.
  • Multi-graph: Displays data in graphs, including monitoring target, time, QPS, response time, errors, and results. By default, the graphs show data for the last hour with the latest data separately listed.
  • Table: Displays data in a table, including the monitoring target, QPS, response time, errors, and results. Data for the last minute is displayed.

Metric description

  • Error/s: Records the rate of RPC errors per minute, which is the total number of errors within the minute divided by 60.
  • Result/s: Records the returned result in the format of “Result: QPS”, where “Result” indicates the RPC result. The HTTP result is consistent with the HTTP ErrorCode.
Thank you! We've received your feedback.