After you install an Application Real-Time Monitoring Service (ARMS) agent for a Java application, ARMS starts to monitor the application. On the Provided Services tab of the application details page, you can view information about the services provided by the application, such as interface calls, message queues, and scheduled tasks.
Prerequisites
Application Monitoring provides a new application details page for users who have enabled the new billing mode. For more information, see Billing (new).
If you have not enabled the new billing mode, you can click Switch to New Version on the Application List page to view the new application details page.
An ARMS agent is installed for the application. For more information, see Application Monitoring overview.
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.
NoteIf the
icon is displayed in the Language column, the application is connected to Application Monitoring. If a hyphen (-) is displayed, the application is connected to Managed Service for OpenTelemetry. In the top navigation bar, click the Provided Services tab.
In the Quick Filter section (icon 1), you can query charts and services by Request Type, Operation, or Host.
In the trend charts section (icon 2), you can view the time series of the number of requests, number of errors, and average time consumed.
Click the
icon. In the dialog box that appears, you can view the metric data in a specific time period or compare the metric data in the same time period on different dates. You can switch between the 
icons to display the data in a column chart or a trend chart. In the service list section (icon 3), you can view the name, request type, and key metrics of each interface defined by the RED Method: rate, errors, and duration.
In the service list, you can perform the following operations:
Click an interface name or click Details, SQL analysis, or NoSQL analysis in the Actions column to view the details of the service. For more information, see the Interface details section.
Click Traces in the Actions column to view the trace details of an interface. For more information, see Trace Explorer.
Supported frameworks
Interfaces provided by the following web frameworks and RPC frameworks are automatically discovered and monitored:
Tomcat 7+
Jetty 8+
Resin 3.0+
Undertow 1.3+
WebLogic 11.0+
SpringBoot 1.3.0+
HSF 2.0+
Dubbo 2.5+
The following message queues are automatically discovered and monitored:
MetaQ
Kafka
Notify
The following scheduled tasks are automatically discovered and monitored.
Only the scheduled tasks of Java applications can be viewed.
XXL-JOB
SchedulerX
JDK-Timer
Interface details
Interface calls
Overview
On the Overview tab, you can view the number of requests, number of errors, average duration, HTTP status codes, and time series of slow calls.
SQL and NoSQL analysis
On the SQL analysis and NoSQL analysis tabs, you can view the lists of SQL and NoSQL requests initiated by the interface. You can also query databases by host. On these tabs, you can locate slow SQL statements or NoSQL statements that cause slow responses of the service.
You can click a SQL or NoSQL database name to view the details of the database. You can also click Traces in the Actions column to view the trace of a SQL or NoSQL statement. For more information, see Trace Explorer.
Upstream and downstream interface calls
On the Upstream and Downstream tabs, you can view the upstream interfaces that call the application and downstream interfaces called by the application, and the relevant metric data, including the number of requests, number of errors, and duration.
Trace Explorer
Trace Explorer allows you to combine filter conditions and aggregation dimensions for real-time analysis based on the stored full trace data. This can meet the custom diagnostics requirements in various scenarios. For more information, see Trace Explorer.
Message queues
Overview
On the Overview tab, you can view the number of requests, number of errors, average duration, and consumption delay. Only the consumption delay data of RocketMQ v4.8.0 and later can be viewed.
SQL and NoSQL analysis
On the SQL analysis and NoSQL analysis tabs, you can view the lists of SQL and NoSQL requests initiated by the interface. You can also query databases by host. On these tabs, you can locate slow SQL statements or NoSQL statements that cause slow responses of the service.
You can click a SQL or NoSQL database name to view the details of the database. You can also click Traces in the Actions column to view the trace of a SQL or NoSQL statement. For more information, see Trace Explorer.
Expenses statistics
On the Expenses Statistics tab, you can view the consumption details of a topic, including the number of requests, number of errors, and duration, from the perspective of a consumer.
Trace Explorer
Trace Explorer allows you to combine filter conditions and aggregation dimensions for real-time analysis based on the stored full trace data. This can meet the custom diagnostics requirements in various scenarios. For more information, see Trace Explorer.
Scheduled tasks
Only the scheduled tasks of Java applications can be viewed.
Overview
On the Overview tab, you can view the number of requests, number of errors, average duration, and time series of scheduling latency.
SQL and NoSQL analysis
On the SQL analysis and NoSQL analysis tabs, you can view the lists of SQL and NoSQL requests initiated by the interface. You can also query databases by host. On these tabs, you can locate slow SQL statements or NoSQL statements that cause slow responses of the service.
You can click a SQL or NoSQL database name to view the details of the database. You can also click Traces in the Actions column to view the trace of a SQL or NoSQL statement. For more information, see Trace Explorer.
Downstream interface calls
On the Downstream tab, you can view the downstream interfaces called by the application, and the relevant metric data, including the number of requests, number of errors, and duration.
Trace Explorer
Trace Explorer allows you to combine filter conditions and aggregation dimensions for real-time analysis based on the stored full trace data. This can meet the custom diagnostics requirements in various scenarios. For more information, see Trace Explorer.