After you install an Application Real-Time Monitoring Service (ARMS) agent for an application, ARMS starts to monitor the application. On the Overview tab of the application details page, you'll see the total requests, errors, and instances, and the time consumed.
Prerequisite
An ARMS agent is installed for the application.
Application Monitoring provides a new application details page for users who have enabled the new billing mode.
If you have not enabled the new billing mode, click Switch to New Version on the Application List page to view the new application details page.
Procedure
Log on to the ARMS console. In the left-side navigation pane, choose .
On the Application List page, select a region in the top navigation bar and click the name of the application that you want to manage.
NoteIcons displayed in the Language column indicate languages in which applications are written.
: Java application
: Go application
: Python applicationHyphen (-): application monitored in Managed Service for OpenTelemetry.
In the top navigation bar, click the Overview tab.
Dashboards
The Overview tab provides dashboard data and CPU information based on whether the application is deployed in an Elastic Compute Service (ECS) instance or a Container Service for Kubernetes (ACK) cluster, and whether the environment is monitored in Managed Service for Prometheus.
If your application is deployed in an ACK cluster that is monitored in Managed Service for Prometheus, the data of Managed Service for Prometheus is displayed in the dashboard. For information about how to use Managed Service for Prometheus to a monitor an ACK cluster, see Monitor an ACK cluster.
If the ACK cluster is not monitored in Managed Service for Prometheus, make sure that the ARMS agent version is 4.1.0 or later. Then, the data of Application Monitoring is displayed. For information about the release notes of the ARMS agent, see Release notes of the ARMS agent for Java.
ECS instance
Section | Visualization style | Description |
Requests | Ticker board | Displays the total number of requests of the application in the specified time period. Day On Day: the percentage of increase or decrease in the number of requests in the specified time period of the current day with the number of requests in the same time period of the previous day. |
Number of errors | Ticker board | Displays the total number of errors during the specified time period. Day On Day: the percentage of increase or decrease in the number of errors in the specified time period of the current day with the number of errors in the same time period of the previous day. |
Average Duration | Ticker board | Displays the average time consumed for the application in the specified time period. Day On Day: the percentage of increase or decrease in the average time consumed for the application in the specified time period of the current day with the average time consumed in the same time period of the previous day. |
Number of instances | Ticker board | Displays the total number of instances in the specified time period. Day On Day: the percentage of increase or decrease in the number of instances in the specified time period of the current day with the number of instances in the same time period of the previous day. |
Requests | Column chart | Shows the trends in the number of requests in the specified time period. The columns with different call types are stacked on top of each other. |
Errors | Column chart with a trend line | Errors: uses a column chart to show the trends in the number of errors in the specified time period. The left y-axis represents the number of errors. Error Rate: adds a trend line to the column chart to show the trends in the error rates in the specified time period. The right y-axis represents the error rates. |
Duration | Trend chart | Shows the trends in the time consumed for the application in the specified time period. Supported values: average time consumed, 99th percentile of the time consumed, 90th percentile of the time consumed, and 75th percentile of the time consumed. |
Peak CPU usage | Honeycomb | Shows the peak CPU utilization of the hosts in the specified time period. Colors:
|
Provided Service Ranking of Requests | Top 5 | Displays five services provided by the application with the most interface requests in the specified time period. Call types:
|
Provided Service Ranking of Errors | Top 5 | Displays five services provided by the application with the most interface errors in the specified time period. Call types:
|
Provided Service Ranking of Average Duration | Top 5 | Displays five services provided by the application with the most time consumed in the specified time period. Call types:
|
Peak CPU Usage Instance Ranking | Top 5 | Displays five hosts with the highest CPU utilization in the specified time period. |
ACK cluster monitored in Managed Service for Prometheus
Section | Visualization style | Description |
Requests | Ticker board | Displays the total number of requests of the application in the specified time period. Day On Day: the percentage of increase or decrease in the number of requests in the specified time period of the current day with the number of requests in the same time period of the previous day. |
Number of errors | Ticker board | Displays the total number of errors during the specified time period. Day On Day: the percentage of increase or decrease in the number of errors in the specified time period of the current day with the number of errors in the same time period of the previous day. |
Average Duration | Ticker board | Displays the average time consumed for the application in the specified time period. Day On Day: the percentage of increase or decrease in the average time consumed for the application in the specified time period of the current day with the average time consumed in the same time period of the previous day. |
Number of instances | Ticker board | Displays the total number of instances in the specified time period. Day On Day: the percentage of increase or decrease in the number of instances in the specified time period of the current day with the number of instances in the same time period of the previous day. |
Requests | Column chart | Shows the trends in the number of requests in the specified time period. The columns with different call types are stacked on top of each other. |
Errors | Column chart with a trend line | Errors: uses a column chart to show the trends in the number of errors in the specified time period. The left y-axis represents the number of errors. Error Rate: adds a trend line to the column chart to show the trends in the error rates in the specified time period. The right y-axis represents the error rates. |
Duration | Trend chart | Shows the trends in the time consumed for the application in the specified time period. Supported values: average time consumed, 99th percentile of the time consumed, 90th percentile of the time consumed, and 75th percentile of the time consumed. |
Peak CPU usage | Honeycomb | Displays the CPU utilization of the application in the specified time period. If the application is deployed in multiple ACK clusters, the data of the first cluster that has data reported is displayed. |
Provided Service Ranking of Requests | Top 5 | Displays five services provided by the application with the most interface requests in the specified time period. Call types:
|
Provided Service Ranking of Errors | Top 5 | Displays five services provided by the application with the most interface errors in the specified time period. Call types:
|
Provided Service Ranking of Average Duration | Top 5 | Displays five services provided by the application with the most time consumed in the specified time period. Call types:
|
Peak CPU Usage Instance Ranking | Top 5 | Displays five application instances with the most CPU utilization in the specified time period. If the application is deployed in multiple ACK clusters, the data of the first cluster that has data reported is displayed. |
Kubernetes cluster (custom data collection)
Section | Visualization style | Description |
Requests | Ticker board | Displays the total number of requests of the application in the specified time period. Day On Day: the percentage of increase or decrease in the number of requests in the specified time period of the current day with the number of requests in the same time period of the previous day. |
Number of errors | Ticker board | Displays the total number of errors during the specified time period. Day On Day: the percentage of increase or decrease in the number of errors in the specified time period of the current day with the number of errors in the same time period of the previous day. |
Average Duration | Ticker board | Displays the average time consumed for the application in the specified time period. Day On Day: the percentage of increase or decrease in the average time consumed for the application in the specified time period of the current day with the average time consumed in the same time period of the previous day. |
Number of instances | Ticker board | Displays the total number of instances in the specified time period. Day On Day: the percentage of increase or decrease in the number of instances in the specified time period of the current day with the number of instances in the same time period of the previous day. |
Requests | Column chart | Shows the trends in the number of requests in the specified time period. The columns with different call types are stacked on top of each other. |
Errors | Column chart with a trend line | Errors: uses a column chart to show the trends in the number of errors in the specified time period. The left y-axis represents the number of errors. Error Rate: adds a trend line to the column chart to show the trends in the error rates in the specified time period. The right y-axis represents the error rates. |
Duration | Trend chart | Shows the trends in the time consumed for the application in the specified time period. Supported values: average time consumed, 99th percentile of the time consumed, 90th percentile of the time consumed, and 75th percentile of the time consumed. |
Peak CPU usage | Honeycomb | Displays the CPU utilization of the application in the specified time period. |
Provided Service Ranking of Requests | Top 5 | Displays five services provided by the application with the most interface requests in the specified time period. Call types:
|
Provided Service Ranking of Errors | Top 5 | Displays five services provided by the application with the most interface errors in the specified time period. Call types:
|
Provided Service Ranking of Average Duration | Top 5 | Displays five services provided by the application with the most time consumed in the specified time period. Call types:
|
Peak CPU Usage Instance Ranking | Top 5 | Displays five application instances with the most CPU utilization in the specified time period. |
Panels
Actions
Click 
above the trend chart to compare data by group and time.
Comparison by group: The options for Groups are Basic fields and Instance tag.
Basic fields: The tags shared by all metrics, which specify the server IP address for group comparison.
Instance tag: In addition to the default instance tags, you can also customize instance tags to enhance the comparison capabilities based on groups. For more information, see Add and use tags.
Comparison by time: Specify the time range for comparison.
Query statements
Click 
above a section to view its Prometheus Query Language (PromQL) statements. In Managed Service for Prometheus or Managed Service for Grafana, customize the settings using the obtained PromQL statements.
In Managed Service for Prometheus, run the PromQL statements to view the metrics on the Metrics Explorer page.
Managed Service for Grafana lets you configure dashboards using PromQL statements. To do this, first integrate data sources.
FAQs
Why is the 99th percentile data not displayed?
By default, the percentile metrics are disabled. To view percentile data, enable the percentile statistics feature on the Custom Configurations page. For more information, see Customize settings for a Java application.
Why is the total number of requests on the Overview page in the old console inconsistent with the actual data from the last 5 minutes?
The data displayed on the Overview page in the old ARMS console includes data from one minute prior to the selected time range. If you select a time range of 5 minutes, data of the last 6 minutes is displayed. If you select a time range of 30 minutes, data of the last 31 minutes is displayed.
Why is the number of slow SQL statements on the Overview page in the old console inconsistent with the number queried using the POP API?
When the POP API is used to query slow SQL statements, it retrieves slow requests related to the databases supported by ARMS, the NoSQL database, and caches. However, the ARMS console queries only slow requests related to the databases supported by ARMS, resulting in the discrepancy.
To ensure that the data queried by the POP API is consistent with the data displayed on the Overview page in the old ARMS console, you can add filter conditions for rpcType to the queries.
Sample code:
QueryMetricByPageRequest.Filters filters2 = QueryMetricByPageRequest
.Filters
.builder()
.key("rpcType")
.value("60|62|63|65|66|67|68|69|58|59")
.build();Why is the number of queried instances greater than the number of running instances?
If the query takes a long time, the destroyed instances are also included in the total count of instances.
Why is the total number of requests on the Overview page in the new console inconsistent with that in the old console?
The Overview page in the new console includes data of scheduled tasks. By contrast, the Overview page in the old console does not include such data.