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 GuideO&MProcess choreographyorchestration planContent of metric alert callback requests
Copy page
Download PDForchestration plan
Content of metric alert callback requests
Copy pageDownload PDFContent of metric alert callback requests
The content of a metric alert callback request includes callback request headers and the callback request body. Learn more.
Callback request headers
Header key | Header value | Description |
x-volc-trace-id | Random UUID | Used for request tracking. |
x-volc-rule-id | { rule_id } | The policy ID. |
Callback request body
Data type
The data type of the request body is application/json.
Request body parameters
Parameter | Type | Example value | Description |
Type | String | Metric | The alert type. Valid value: Metric (threshold). |
AccountId | String | 210005**** | The account ID. |
RuleName | String | Test alert policies | The policy name. |
RuleId | String | 193525924306958**** | The policy ID. |
Namespace | String | VCM_FileNAS | The product type. |
SubNamespace | String | latency | The dimension. |
Level | String | critical | The alert level: Value:
|
HappenedAt | String | 2024-04-11 14:51:01(UTC+08:00) | The time when the alert is triggered. |
RuleCondition | String | An alert is triggered when any of the metrics reaches the threshold: The average CPU usage exceeds 90% for 10 consecutive cycles (1 cycle = 1 minute). The average memory usage exceeds 90% for 10 consecutive cycles (1 cycle = 1 minute). | The details of the alert policy. |
Resources | Object | - | The details of the resource for which the alert notification is sent. For the specific format, see Resource structure. |
RecoveredResources | Object | - | The details of the resource for which the alert cleared notification is sent. For the specific format, see Resource structure. |
NoDataResources | Object | - | The details of the resource for which the no data alert is triggered. For the specific format, see Resource structure. |
NoDataRecoveredResources | Object | - | The details of the resource for which the no data alert is cleared. For the specific format, see Resource structure. |
Resource structure
Parameter | Type | Example value | Description |
Id | String | i-ydvvy21se8r9cxxi**** | The resource ID. |
Name | String | enas-cn0445d06f**** | The resource name. |
Region | String | cn-beijing | The region. |
FirstAlertTime | Int | 1664332705 | The time when the alert is triggered for the first time. |
LastAlertTime | Int | 1664332705 | The time when the alert is triggered. |
Metrics | Object | - | The metrics for which parsing succeeded. For threshold alerts, see this field. For the specific format, see Metric structure. |
NoDataMetrics | Object | - | The metric for which no data points are collected. For more information about the no data alert, see this field. |
DroppedMetrics | Object | - | The metric for which parsing failed. For example, in numerical calculations related to alerts, a common scenario results in NaN: when the calculation logic involves division, if the dividend is 0, no valid number can be derived, and the system regards this result as unparsable. |
AlertGroupId | String | 68746e79885576cda23**** | The alert history ID. |
Dimensions | Object | - | The dimension information of the resource. For the specific format, see Dimension structure. |
Metric structure
Parameter | Type | Example value | Description |
Name | String | Nfsv3WriteLat**** | The metric name. |
Unit | String | ms | The unit of the metric. |
Threshold | Float | 1 | The threshold of the metric in this policy. |
CurrentValue | Float | 0.0001 | The current value of the metric. |
Description | String | NFSv3 write latency | The description of the metric. |
Warning | Bool | true | The alert triggered by the metric. tip This field exists only when the metric triggers an alert. |
Dimension structure
Parameter | Type | Example value | Description |
Name | String | ResourceID | The dimension of the metric. |
Value | String | i-ydvvy21se8r9cxxi**** | The value of the dimension. |
NameCN | String | InstanceID | The Chinese name of the dimension. |
Sample request body
tip
You can skip parameters with no description in the actually received request body. These parameters do not affect your ability to obtain details of the alert notification.
{
"AccountId": "210005****",
"HappenedAt": "2025-07-22 20:24:44(UTC+08:00)",
"Level": "warning",
"Namespace": "VCM_ECS",
"NoDataResources": [
{
"AlertGroupId": "68746e79885576cda23****",
"Dimensions": [
{
"Description": "Instance",
"Name": "ResourceID",
"Value": "i-ydvvy21se8r9cxxi****"
},
{
"Description": "Private Network",
"Name": "IP.Inside",
"Value": "192.xx.xx.17"
},
{
"Description": "Public Network",
"Name": "IP.Outside",
"Value": "-"
}
],
"FirstAlertTime": 1752461461,
"Id": "i-ydvvy21se8r9cxxi****",
"LastAlertTime": 1753187084,
"Name": "node-0000002",
"NoDataMetrics": [
{
"CurrentValue": 0,
"Description": "CPU Usage",
"Name": "CpuTotal",
"Threshold": 0,
"Unit": "%"
},
{
"CurrentValue": 0,
"Description": "Memory Usage",
"Name": "MemoryUsedUtilization",
"Threshold": 0,
"Unit": "%"
}
],
"ProjectName": "default",
"Region": "cn-beijing",
"Tags": {
"volc:auto_scaling:scalingGroupId": "scg-ydvuyd19vml2a08a****",
"volc:vke:cluster-id": "cd0imidbrtbp46pe4****",
"volc:vke:created-by-cluster-id": "cd0imidbrtbp46pe4****",
"volc:vke:createdby-vke-flag": "true",
"volc:vke:nodepool-id": "pd0imidrrtbp46pe4****",
"volc:vke:used-by-vke-cluster": "true",
"volc:vke:vpc-id": "vpc-2byvea76anx8g2dx0een8****"
}
},
{
"AlertGroupId": "68746e79885576cda236****",
"Dimensions": [
{
"Description": "Instance",
"Name": "ResourceID",
"Value": "i-ydvvcuyry8ygp2fc****"
},
{
"Description": "Private Network",
"Name": "IP.Inside",
"Value": "192.xx.xx.3"
},
{
"Description": "Public Network",
"Name": "IP.Outside",
"Value": "-"
}
],
"FirstAlertTime": 1752461461,
"Id": "i-ydvvcuyry8ygp2fc****",
"LastAlertTime": 1753187084,
"Name": "node-0000001",
"NoDataMetrics": [
{
"CurrentValue": 0,
"Description": "CPU Usage",
"Name": "CpuTotal",
"Threshold": 0,
"Unit": "%"
},
{
"CurrentValue": 0,
"Description": "Memory Usage",
"Name": "MemoryUsedUtilization",
"Threshold": 0,
"Unit": "%"
}
],
"ProjectName": "default",
"Region": "cn-beijing",
"Tags": {
"volc:auto_scaling:scalingGroupId": "scg-ydvuyd19vml2a08a****",
"volc:vke:cluster-id": "cd0imidbrtbp46pe4****",
"volc:vke:created-by-cluster-id": "cd0imidbrtbp46pe4****",
"volc:vke:createdby-vke-flag": "true",
"volc:vke:nodepool-id": "pd0imidrrtbp46pe4****",
"volc:vke:used-by-vke-cluster": "true",
"volc:vke:vpc-id": "vpc-2byvea76anx8g2dx0een8****"
}
}
],
"Project": "default",
"RuleCondition": "No data alarm :\nCPU usage rate: no data for 10 cycles (1 cycle = 1 minute)\memory usage rate: no data for 10 cycles (1 cycle = 1 minute)",
"RuleId": "193525924306958****",
"RuleName": "instance_test&test",
"SubNamespace": "Instance",
"Type": "MetricsNoData"
}
Last updated: 2025.09.17 10:14:54
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
