The Instance Monitoring page shows basic information about application instances, such as request count, error count, average response time, and slow calls. You can also view network information, such as the number of received packets, TCP round-trip time (RTT), retransmission count, TCP drop count, and the number of sent packets.
Procedure
-
Log on to the ARMS console. In the left-side navigation pane, choose .
-
In the top navigation bar, select a region.
-
On the Application List page, click the name of the application.
-
In the top navigation bar, click Instance Monitoring.
-
In the Quick Filter area, you can filter the charts and the instance list by instance name.
-
The trend chart area shows time-series charts of the instance's CPU and memory usage.
Click the
icon to view statistics for the metric over a specific time period or compare statistics for the same period on different dates in the dialog box. Click the
icon to switch between a column chart and a trend chart. -
The instance list area shows information such as instance CPU usage, memory usage, request count, average response time, and error count.
In the instance list, you can perform the following operations:
-
Click an instance IP address to view the instance's details. For more information, see Instance details.
-
In the Actions column, click Overview. The panel on the right shows an overview of the instance, including its request count, error count, and average response time.

-
In the Actions column, click Traces to view the instance's trace details. For more information, see Trace Explorer.
-
-
Instance details
Overview
The Overview tab shows the request count, error count, average response time, and slow calls for the target interface.

Network monitoring
The Network monitoring tab displays the number of packets received by the application, TCP RTT, retransmission count, TCP drop count, and the number of sent packets.

Container monitoring
To use container monitoring, connect your container service to Managed Service for Prometheus. For more information, see Prometheus instance for Container Service.
The Container monitoring tab shows container-level metrics for CPU, memory, disk, load, network traffic, and network packets.
This page contains four subtabs: Overview, Network monitoring, Container monitoring, and Trace Explorer. When you select the Container monitoring subtab, the Overview section displays the pod's namespace, node name, age, status, phase, and restart count, and the requests and limits for CPU and memory. The Containers table lists the status, image, and resource requests for each container. The Warning Events section shows warning events. The Resource section displays charts for monitoring metrics such as Memory Usage, Memory Failcnt, Network Error (Percent), CPU Usage (%), CPU Usage By Cores, CPU Load (10s), and CPU Throttled Percent.
Trace Explorer
Trace Explorer analyzes stored trace data in real time. Combine filter conditions and aggregation dimensions for custom diagnostics. For more information, see Trace Explorer. On the Trace Explorer page in the trace console, use the search condition serviceName="service-product-skywalking" AND attributes.ali.trace.rpc="HikariCP/Connection/close" to query trace data. The top of the page displays a bar chart of calls, a chart of HTTP errors, and a line chart for latency percentiles (p50, p90, p95, p99, and average response time). The quick filter panel on the left allows you to filter by Status, Duration, Interface Name, and Host Address. The main trace list shows approximately 15,000 call records. All records have the interface name HikariCP/Connection/close, the application name service-product-skywalking, a duration of 1 ms, and a normal status. The panel on the right displays the slow trace analysis results, which include statistical dimensions such as statusCode and kind.
Contact us
If you have any questions about using Application Monitoring eBPF Edition, join the DingTalk group (ID: 35568145) to obtain technical support.