Application Real-Time Monitoring Service (ARMS) provides multiple sub-services, such as Application Monitoring, Browser Monitoring, and Prometheus Service. To meet different requirements, each sub-service provides multiple editions, such as the Trial Edition, Basic Edition, and Pro Edition. This topic compares the features of different editions of ARMS sub-services.
Application Monitoring
ARMS Application Monitoring is an application performance monitoring tool. It combines the industry-leading theoretical models of distributed application monitoring and tracing with the practices of Alibaba Group. This sub-service provides more comprehensive, real-time application monitoring services.
Feature | Basic Edition | Pro Edition |
---|---|---|
Application overview | ||
Displays application statistics, such as the total number of requests, average response
time, and the number of real-time instances. It also displays time series charts such
as the number of service requests and the service response time. The application overview
feature allows you to view the overall performance of applications. ![]() |
![]() |
![]() |
Automatically identifies the call relationships between applications or between APIs,
and generates a real-time topological graph. ![]() |
![]() |
![]() |
Displays the health status of applications, services, and hosts, and displays the
upstream and downstream dependencies of the applications. ![]() |
![]() |
![]() |
Application details | ||
Overview Automatically identifies the call relationships between applications or between APIs, and generates a real-time topological graph.![]() |
![]() |
![]() |
Monitors heap memory metrics, non-heap memory metrics, direct buffer metrics, memory-mapped
buffer metrics, garbage collection (GC) details, and the number of JVM threads. ![]() |
![]() |
![]() |
Monitors thread pool metrics such as the number of core threads, number of existing
threads, maximum number of allowed threads, number of active threads, number of submitted
tasks, and maximum number of tasks allowed in a task queue. ![]() |
![]() |
![]() |
Monitors host metrics such as CPU, memory, disk, load, network traffic, and network
packets. ![]() |
![]() |
![]() |
SQL analysis, NoSQL analysis, exception analysis, and error analysis Displays and analyzes SQL statements, exceptions, and errors with respect to dimensions such as the application, instance, and API.![]() |
![]() |
![]() |
Displays API snapshots with respect to dimensions such as the application, instance,
and API. ![]() |
![]() |
![]() |
API invocation | ||
Overview Automatically identifies the call relationships between applications or between APIs, and generates a real-time topological graph.![]() |
![]() |
![]() |
SQL analysis and NoSQL analysis Analyzes SQL statements with respect to dimensions such as the application, instance, and API. This allows you to diagnose the causes of slow calls.![]() |
![]() |
![]() |
Analyzes the drill-down information of exceptions with respect to dimensions such
as the application, instance, and API. ![]() |
![]() |
![]() |
Displays the statistics of application errors and HTTP status codes. ![]() |
![]() |
![]() |
Displays the statistics of the APIs and their invocation performance metrics. These statistics include the number of requests, response time, and number of errors. | ![]() |
![]() |
Displays API snapshots with respect to dimensions such as the application, instance,
and API. ![]() |
![]() |
![]() |
Event center
Manages, stores, analyzes, and displays event data that is generated by cloud services in a centralized manner. |
![]() |
![]() |
Database invocation | ||
Overview Automatically identifies the call relationships between applications and databases, and generates a real-time topological graph. |
![]() |
![]() |
Analyzes SQL statements with respect to dimensions such as the application, instance, and API. This allows you to diagnose the causes of slow calls. | ![]() |
![]() |
Analyzes the drill-down information of exceptions with respect to dimensions such as the application, instance, and API. | ![]() |
![]() |
Call sources
Displays the APIs that are used to call databases. |
![]() |
![]() |
Displays API snapshots with respect to dimensions such as the application, instance, and API. | ![]() |
![]() |
Other monitoring features | ||
Calls to external services Displays the statistics of metrics such as the number of external requests, response time, number of errors, and HTTP status codes. |
![]() |
![]() |
Displays the statuses of topic publishing and subscription of Message Queue for Apache RocketMQ. | ![]() |
![]() |
Application diagnosis | ||
Continuously monitors the application for 5 minutes and provides reports for all trace data during this period. | ![]() |
![]() |
Exception analysis Displays the number of occurrences, name, related API, and summary of each exception in an aggregated manner. |
![]() |
![]() |
Displays the thread-specific statistics of CPU time consumption and the number of threads for each type. This feature records and aggregates the method stacks of threads every 5 minutes to simulate the code execution process. | ![]() |
![]() |
Arthas helps developers diagnose issues in the production environment of Java applications.
It utilizes bytecode enhancement to allow developers to check the application status
without restarting running Java virtual machine (JVM) processes. ![]() |
![]() |
![]() |
Application settings | ||
Provides multiple methods to install the agent and an easy way to delete applications. | ![]() |
![]() |
Modify the settings of the trace sampling rate and the agent switch Allows you to set the trace sampling rate, agent switch, thresholds, and filtering rules for invalid API calls. |
![]() |
![]() |
Associate trace IDs with business logs Associates trace IDs with the business logs of an application. This way, when an error occurs in the application, you can access the business logs associated with trace IDs to troubleshoot the error.![]() |
![]() |
![]() |
Trace query | ||
Allows you to query and view the distributed trace and local call method stack with respect to dimensions such as the call type, response time, application name, IP address, and API. | ![]() |
![]() |
Alerts and dashboards | ||
Allows you to configure alert rules based on the metrics of Application Monitoring. | ![]() |
![]() |
Allows you to configure interactive dashboards based on specific requirements for Application Monitoring. | ![]() |
![]() |
Supported agents | ||
Supports Tomcat, Jetty, Spring Boot, Dubbo, High-Speed Service Framework (HSF), HttpClient, MySQL, Oracle, and all Alibaba Cloud middleware services. | ![]() |
![]() |
API calls | ||
Allows you to obtain application monitoring results by calling API operations. | ![]() |
![]() |
Retention policy for monitoring data | ||
Displays the retention period of time series data, such as transactions per second (TPS) and response time, that is generated when you call applications to perform query and statistical operations. | 3 days | 90 days |
Displays the retention period of detailed data, such as distributed call stacks, that is generated when you call applications to perform query and diagnostic operations. | 1 day | 30 days |
Activation link | Activate now | Activate now |