Elastic Compute Service
Elastic Compute Service
Elastic Compute Service
Document
Elastic Compute Service
What's New
Announcement
OpenAPI related
Pricing and quotas are related
About products and plugins
Feature discontinuation
Overview
Billing
Billable items
Billing methods
Billing methods change
Getting Started
User Guide
Instances
Instance types
X86 Computing
Elastic Bare Metal Server
Heterogeneous Computing
Select instance billing method
Spot instance
Elastic Scheduled Instance
Offsetting Resources
Reserved Instances
Buying ECS instances
Logging in to an instance
Logging in to a Linux instance
Managing instance status
Modifying instance types
Using instance user data and metadata
Instance metadata
Images
Public images
veLinux images
Custom images
Importing custom images
Creating custom images
Image detection
End of life (EOL) of image
Elastic Block Storage
Basic volume operations
Partitioning and formatting a volume
Extending a volume
EBS Agent
Snapshots
Basic snapshot operations
Auto snapshot policies
DataInsights
Network
Network interface and IP address
IP Address
IPv4 address
Security group
Security
Passwords and key pairs
Deployment and scaling
Monitoring
Monitoring metrics
Event monitoring
Local volume event O&M
Method 1: Solve the local volume failure by replacing the faulty volume
O&M
Cloud assistant
Managing agents
Process choreography
Common operation and maintenance tasks
Batch operations on instances
Batch operations on EBS Volumes
Batch operations on images
Temporary upgrade of bandwidth
Managing application updates
orchestration plan
Patch management
Managing patch plans
Managing patch baselines
IAM
Tags and projects
Best Practices
AI applications
OpenClaw (formerly Moltbot)
Quickly deploying OpenClaw via application templates
Quickly deploying OpenClaw via marketplace images
Manually deploying OpenClaw
Self-service website creation
Building environments
Building a Web environment (Windows)
Building applications
Building FTP site
Deploying databases
Building game servers
Building websites
Building a WordPress blog
Building multiple websites
Manage software sources for Linux instances
AIGC practices
Performance test
Network performance test
Instance configuration
Setting up AD Domain Services on Windows OS
Windows Multi - User Login
Changing screen resolution
Instance data
Uploading or downloading files
Data restoration
ECS instance local time synchronization
Volume
Monitoring
Security
Images
Kernel fine-tuning
O&M
Troubleshooting
Remote log in issue
Linux operating system issue
Windows operating system issue
SSH log in issue
Operating system issue
veLinux operating system issue
Linux operating system issue
Windows operating system issue
Instance status issue
Instance unable to start issue
High instance load issue
GPU instances issue
Network connection issue
Network configuration issue
Storage classes issue
EBS Volume issue
Local Disk issue
Logs and monitoring issue
Third - party software issue
API Reference
Regions and availability zones
Instances
Images
HPC clusters
Key pairs
Tags
Volumes
Reserved storage capacity
Snapshot
Auto snapshot policy
Monitoring
Deployment sets
Launch templates
Cloud assistant
Patch management
SDK reference
CLI Reference
FAQ
Dedicated Host DDH
What's New
Billing
User Guide
Manage Dedicated Host
Manage Dedicated Host Cluster
Manage ECS instances
Monitoring and O&M
API reference
proprietary host
- Documentation
Elastic Compute ServiceElastic Compute ServiceUser GuideMonitoringMonitoring overview
Copy page
Download PDFMonitoring
Monitoring overview
Copy pageDownload PDFMonitoring overview
Volcano Engine provides monitoring services for ECS instances. Comprehensive monitoring metrics, event-based monitoring, and visualized data display help you track the running state of resources created. You can also customize metric thresholds, alert notifications, event monitoring rules, and other capabilities. This allows you to be timely informed when the instance has an exception and therefore to run your businesses stably.
Metric monitoring
ECS instances can be monitored based on various monitoring metrics.
tip
The following table provides methods for you to view monitoring metrics for one instance. To view monitoring metrics of operating systems for multiple instances, go to the Cloud Monitor console.
Feature/Operation | Description |
Feature/Operation | Description |
Display the Chinese and English names, purposes, descriptions, and other information about ECS monitoring metrics. | |
Monitor basic performance metrics of the instance, such as CPU, network, and disk. This feature can help you learn the overall load and resource consumption of instances. | |
Monitor the operating system of the instance, including its CPU, memory, disk, network, and network interface. This can help you to obtain deeper and more accurate information about instance operations. | |
Monitor the TCP connection state of the instance operating system. Monitoring metrics include TCP bytes sent/received and connection retransmission count for connections between local and remote IP addresses. This can help you timely detect the TCP connection state of the instance operating system. | |
Monitor the total number of active processes and the top 5 CPU-consuming processes of the Elastic Compute Service (ECS) in real time, including metrics such as CPU usage and memory usage. This helps to understand the extent of system resource consumption caused by processes, quickly identify processes consuming excessive resources, and provides the ability to add critical processes for visualization and monitoring of their process count. | |
Only monitor the metrics of GPU instances, such as GPU utilization rate, GPU memory utilization rate, and GPU temperature. This can help you easily learn about instance information, such as GPU memory usage and GPU utilization rate. | |
Only monitor the RDMA network metrics of GPU Compute Service (GPU) instances. Monitoring metrics include RDMA network inflow/outflow rate, the number of received/sent RDMA data packets, the number of RDMA network outbound/inbound suspended packets, and other metrics. This feature can help you learn RDMA network-related information of instances. |
If you need the Cloud Monitor to send you alert notifications when the monitoring metrics reach the specified thresholds, you can configure alert rules yourself.
Feature/Operation | Description |
Feature/Operation | Description |
Alarm templates (alarm strategies) for ECS instance CPU and disk resource usage are pre-configured by default. You can enable them with one click to receive timely alerts about instance resource issues. | |
You can configure alarm strategies as needed to monitor more metrics. | |
You can view the alert records of ECS instances in the console to understand their abnormal metric trends. |
Event monitoring
ECS instances support event-level monitoring. For details, refer to:
- Configuring event monitoring notifications: If you need to receive alert notifications when a specified monitoring event is triggered in an instance, you can configure event alert rules and notification channels.
Instance health state monitoring
The monitoring feature for instance health state automatically detects the software and hardware running information of the instance, calculates the health state of the instance in summary, and helps you quickly understand the instance's health state through the console. For details, refer to Viewing instance health status.
Last updated: 2026.06.18 17:49:50
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
