You can use Application Monitoring of Application Real-Time Monitoring Service (ARMS) to monitor applications. After you install an ARMS agent for an application, ARMS starts monitoring it. You can view data like application topology, traces, abnormal transactions, slow transactions, and SQL analysis.
Application lifecycle
A lifecycle starts when the application is connected to Application Monitoring, and ends when it's deleted. Throughout its lifecycle, the application may be in different states.
State | Property | Description |
Normal | Stable state | If the application is connected to Application Monitoring and receives external traffic, monitoring becomes active. You can query the monitoring data in the ARMS console. |
Slow | Intermediate state | When the average time consumed for the application reaches the specified threshold, the application enters an intermediate state. The Slow state may occur due to many reasons, such as high load of basic resources, slow response of external dependencies, and high self-load. |
Failed | Intermediate state | When the application encounters an error, the application enters an intermediate state. The Failed state indicates that the application has failed service calls within a period of time. |
No Data | Offline or no traffic | When the ARMS console does not display the monitoring data of the application, the application enters the No Data state. This state is triggered when a network problem occurs, the application is running abnormally, or the application is not accessed by external traffic. |
Feature overview
Feature | Description |
Displays key metrics such as request count, fault count, average response time, and the number of running instances. | |
Visualizes the call relationships between services within the application, helping you understand service dependencies and architecture. | |
Shows details of services exposed by the application, including API endpoints, message queue consumers, and scheduled tasks. | |
Lists services the application relies on, such as external APIs, databases, and message queues. | |
Enables real-time analysis of distributed traces. You can combine custom filter conditions and aggregation dimensions to diagnose issues across different scenarios. | |
Provides visibility into instance-level metrics, including CPU, memory, garbage collection (GC), and JVM memory usage. | |
Helps identify and analyze application exceptions and error patterns. | |
Allows you to locate business-level exceptions using structured business logs, enabling precise root cause analysis. |
Notes
The application list contains applications monitored both in ARMS Application Monitoring and Managed Service for OpenTelemetry.
If an application is renamed by modifying the startup parameter
arms.appName, it enters the No Data state and is still displayed in the application list. If you no longer need the application, you can delete its data.