Tencent Cloud Observability Platform
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Application Performance Management
- Pay-as-you-go (Postpaid)
- Packages (Prepaid)
- Mobile App Performance Monitoring
- Real User Monitoring
- Cloud Automated Testing
- Prometheus Monitoring
- Pay-as-You-Go (Postpaid)
- Quick Start
- EventBridge
- Cloud Product Monitoring
- Tencent Cloud Service Metrics
- Microservice
- Networking
- TencentDB
- TencentDB for Redis Monitoring Metrics
- CPM
- CDN And EdgeOne
- Operation Guide
- Cloud Monitoring Overview
- Monitoring View
- CM Connection to Grafana
- Troubleshooting
- Application Performance Management
- Access Guide
- Accessing Go Application
- Accessing Java Application
- Accessing Python Application
- Accessing Node.js Application
- Accessing PHP Application
- Accessing .NET Application
- Operation Guide
- Resource Management
- Application Monitoring
- Application Diagnosis
- Database Call Monitoring
- Access Management
- Alarm Service
- System Configuration
- Associate Logs
- Inject TraceID Into Logs
- Practical Tutorial
- Parameter Information
- APM Data Protocol Standard
- Mobile App Performance Monitoring
- Access Guide
- Android Use Cases
- iOS Use Cases
- Tencent Cloud Real User Monitoring
- Operation Guide
- Application Management
- Access Management
- Resource Tag
- Connection Guide
- Web Use Cases
- Cloud Automated Testing
- Operation Guide
- Creating Test Task
- Testing Statistics
- Access Management
- References
- Testing Nodes
- FAQs
- Performance Testing Service
- Operation Guide
- Performance Testing in Script Mode
- Script Examples
- HTTP-based Performance Testing
- Performance Testing in JMeter Mode
- Project Management
- Scenario Management
- Advanced Configuration
- Export Stress Test Indicators
- Traffic Recording
- Performance Testing Report
- Access Control
- Alarm Management
- Tag Management
- Practice Tutorial
- JavaScript API List
- pts/http
- Response
- pts/dataset
- pts/grpc
- pts/jsonpath
- pts/redis
- pts/url
- URL
- pts/util
- pts/ws
- pts/socketio
- socketio
- pts/socket
- Prometheus Monitoring
- Product Introduction
- Access Guide
- EMR Integration
- Java Application Integration
- Exporter Integration
- Operation Guide
- Instance
- Recording Rule
- Alerting Rule
- Access Control
- TKE Metrics
- Practical Tutorial
- Terraform
- Grafana
- Operation Guide
- Instance
- Tencent Cloud Service Integration
- Plugin Management
- Dashboard
- Operation Guide
- Configuring Dashboard
- Monitoring Charts
- Creating Chart
- Use Cases of Different Chart Types
- Alarm Management
- Console Operation Guide
- Alarm Policy
- Configuring alert trigger conditions
- Alarm Notification
- Alarm Callback
- Alarm Receiving Channels and SMS Quota
- Dynamic Threshold Alarm
- Silencing Alarm
- EventBridge
- Product Introduction
- Practical Tutorial
- Migrating Event Alarm
- FAQs
- Related Agreements
- API Documentation
- Making API Requests
- Monitoring Data Query APIs
- Alarm APIs
- Notification Template APIs
- Legacy Alert APIs
- Prometheus Service APIs
- Grafana Service APIs
- Event Center APIs
- TencentCloud Managed Service for Prometheus APIs
- Monitoring APIs
DocumentationTencent Cloud Observability PlatformCloud Product MonitoringTencent Cloud Service MetricsCVM
CVM
Last updated: 2024-08-01 16:28:19
Namespace
Namespace=QCE/CVM
Monitoring Metrics
CPU Monitoring
Parameter | Metric | Description | Unit | Dimension | Statistical Period |
CPUUsage | CPU utilization | Percentage of CPU used in real time during machine operation | % | InstanceId | 10s, 60s, 300s,
3600s, 86400s |
CpuLoadavg | 1-minute CPU load | Average number of tasks that are using and waiting to use the CPU in one minute (this metric is unavailable on Windows) | - | InstanceId | 10s, 60s, 300s,
3600s, 86400s |
Cpuloadavg5m | 5-minute CPU load | Average number of tasks that are using and waiting to use the CPU in five minutes (this metric is unavailable on Windows) | - | InstanceId | 60s, 300s,
3600s |
Cpuloadavg15m | 15-minute CPU load | Average number of tasks that are using and waiting to use the CPU in 15 minutes (this metric is unavailable on Windows) | - | InstanceId | 60s, 300s,
3600s |
BaseCpuUsage | Basic CPU utilization | The basic CPU utilization is collected and reported through the host, and the data can be viewed without the installation of the monitoring component. The data can still be continuously collected and reported even when the load of the CVM is high | % | InstanceId | 10s, 60s, 300s,
3600s, 86400s |
GPU Monitoring
Parameter | Metric | Description | Unit | Dimension | Statistical Period |
GpuMemTotal | Total GPU memory | Total GPU memory | MB | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
GpuMemUsage | GPU memory utilization | GPU memory utilization | % | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
GpuMemUsed | GPU memory usage | Evaluates the GPU memory used by the load | MB | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
GpuPowDraw | GPU power usage | GPU power usage | W | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
GpuPowLimit | Total GPU power consumption | Total GPU power consumption | W | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
GpuPowUsage | GPU power utilization | GPU power utilization | % | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
GpuTemp | GPU temperature | Evaluates the GPU heat dissipation status | °C | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
GpuUtil | GPU utilization | Evaluates the computing power consumed by the load, which is the percentage of non-idle state | % | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
Network Monitoring
Parameter | Metric | Description | Unit | Dimension | Statistical Period |
LanOuttraffic | Private outbound bandwidth | Average outbound traffic of the private ENI per second | Mbps | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
LanIntraffic | Private inbound bandwidth | Average inbound traffic of the private ENI per second | Mbps | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
LanOutpkg | Private outbound packets | Average number of outbound packets of the private ENI per second | Count/s | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
LanInpkg | Private inbound packets | Average number of inbound packets of the private ENI per second | Count/s | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
WanOuttraffic | Public outbound bandwidth | Average outbound traffic rate over the public network per second. The value at the minimum granularity is calculated by 10-second total traffic/10 seconds. This value is the sum of public network outbound/inbound bandwidth of EIP, CLB, and CVM | Mbps | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
WanIntraffic | Public inbound bandwidth | Average inbound traffic rate over the public network per second. The value at the minimum granularity is 10-second total traffic divided by 10 seconds. This value is the sum of public network outbound/inbound bandwidth of EIP, CLB, and CVM | Mbps | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
WanOutpkg | Public outbound packets | Average number of outbound packets of the public ENI per second | Count/s | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
WanInpkg | Public inbound packets | Average number of inbound packets of the public ENI per second | Count/s | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
AccOuttraffic | Public outbound traffic | Average outbound traffic of the public ENI per second | MB | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
TcpCurrEstab | TCP connections | Number of TCP connections in ESTABLISHED status | - | InstanceId | 10s, 60s, 300s,
3600s, 86400s |
TimeOffset | Difference between server UTC time and NTP time | Difference between server UTC time and NTP time | s | InstanceId | 60s, 300s,
3600s |
Memory Monitoring
Parameter | Metric | Description | Unit | Dimension | Statistical Period |
MemUsed | Memory usage | The amount of memory used by the user, excluding caches and buffers, which is total memory minus available memory (including buffers and caches) | MB | InstanceId | 10s, 60s, 300s, 3600s, 86400s |
MemUsage | Memory utilization | Ratio of the used memory (excluding caches, buffers, and the remaining memory) to the total memory | % | InstanceId | 10s, 60s, 300s,
3600s, 86400s |
Disk Monitoring
Parameter | Metric | Description | Unit | Dimension | Statistical Period |
CvmDiskUsage | Disk utilization | Percentage of the used capacity of all disks to the total capacity (maximum value among all disks) | % | InstanceId | 60s, 300s |
DiskUsage | Disk utilization | Disk utilization | % | InstanceId | 60s, 300s, 3600s, 86400s |
Note:
1. Basic metric data (such as CPU and memory) and alarm time (local time of your CVM instance) can be obtained only after the CVM monitor component Agent as described in Installing CVM Agents is installed. If the local time of you CVM instance is not UTC/GMT+08:00, the time of the monitoring data of the instance will not be the local time (UTC/GMT+08:00) of the instance.
2. Ways of installing an Agent:
Select Tencent Cloud Observability Platform when purchasing a CVM instance to automatically install an Agent.
Manually install the Agent as instructed in Installing CVM Agents.
3. The statistical granularity (
period) may vary by metric. You can call the DescribeBaseMetrics API to obtain the period supported by each metric.Dimensions and Parameters
Parameter | Dimension | Description | Format |
Instances.N.Dimensions.0.Name | InstanceId | Dimension name of the CVM instance ID | Enter a string-type dimension name, such as InstanceId |
Instances.N.Dimensions.0.Value | InstanceId | Specific CVM instance ID | Enter a specific instance ID, such as ins-mm8bs222 |
Input Parameters
To query the monitoring data of a CVM instance, use the following input parameters:
&Namespace=QCE/CVM
&Instances.N.Dimensions.0.Name=InstanceId
&Instances.N.Dimensions.0.Value=Specific CVM instance ID
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No