ARMS application monitoring overview - Application Real-Time Monitoring Service

After you install an ARMS agent for an application, ARMS starts monitoring it. You can then view application topology, traces, abnormal and slow transactions, and SQL analysis.

Application lifecycle

An application lifecycle starts when the application connects to ARMS and ends when it is deleted. The application transitions through the following states.

State	Property	Description
Normal	Stable state	The application is connected and receiving external traffic. Monitoring data is available in the ARMS console.
Slow	Intermediate state	Average response time exceeds the configured threshold. Common causes include high resource load, slow external dependencies, or high application load.
Failed	Intermediate state	The application has failed service calls within a given time period.
No Data	Offline or no traffic	No monitoring data is available. This state occurs when the application has network issues, is running abnormally, or receives no external traffic.

Feature overview

Feature	Description
Application Overview	Shows response time, request count, error count, and instance count.
Application topology	Shows the topological relationships among services of the application.
Provided Services	Lists services the application provides, including interface calls, message queues, and scheduled tasks.
Dependencies	Lists services the application depends on, including external calls, database calls, and message queues.
Trace Explorer	Combines filters and aggregation dimensions for real-time analysis on stored full trace data to support custom diagnostics.
Instance monitoring for Java applications	Shows instance-level basic metrics, GC, and JVM memory usage.
Continuous profiling for Java applications	Identifies CPU, memory, and I/O bottlenecks in Java programs with statistics by method name, class name, and line number.
Thread profiling	Shows per-thread CPU time and thread counts. Use thread profiling to locate threads or methods with high CPU consumption.
Arthas diagnostics	Views program execution details through bytecode enhancement without restarting the JVM.
Exception analysis	Shows application exceptions.
Log analysis	Analyzes logs to identify application exceptions.

Usage notes

The application list contains applications monitored both in ARMS Application Monitoring and Managed Service for OpenTelemetry.
If you rename an application by modifying the arms.appName startup parameter, it enters the No Data state but remains in the application list. Delete the application data if it is no longer needed.