All Products
Search
Document Center

Cloud Monitor:Application Monitoring

Last Updated:Jun 08, 2026

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.

image

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

Entity details

Shows key metrics: request count, fault count, average response time, and running instance count.

Associated topology

Visualizes call relationships between services to reveal dependencies and architecture.

Provisioned services

Lists services exposed by the application: API endpoints, message queue consumers, and scheduled tasks.

Dependent services

Lists external dependencies: APIs, databases, and message queues.

Trace Explorer

Analyzes distributed traces in real time. Combine custom filters and aggregation dimensions to diagnose issues across scenarios.

Java Application Instance Monitoring

Tracks instance-level metrics: CPU, memory, GC, and JVM memory usage.

Exception analysis

Identifies and analyzes application exceptions and error patterns.

Log analysis

Locates business-level exceptions through structured business logs for root cause analysis.

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.