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 event alert callback requests
Copy page
Download PDForchestration plan
Content of event alert callback requests
Copy pageDownload PDFContent of event alert callback requests
The content of an event 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-event-id | { event_id } | The event 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 | Event | The alert type. Valid value: Event. |
AccountId | String | 210035**** | The account ID. |
Region | String | cn-beijing | The region. |
Source | String | ecs | The event source, which is the product type. |
ProjectName | String | default | The project name. |
Id | String | 194069710419630**** | The unique event ID. |
EventType | String | ecs:Disk:DiskError.Redeploy.Executing | The event name. |
DescriptionCN | String | Instance redeployment caused by disk failures: in progress. | The Chinese name of the event. |
HappenedAt | Int64 | 1664332705 | The time when the event occurs. |
Details | Object | - | The original event text. |
Rules | Object | - | The event rule details. For the specific format, see Rule structure. |
Rule structure
Parameters | Type | Example value | Description |
RuleId | String | 194069687426716**** | The policy ID. |
RuleName | String | Test event alert 1 | The policy name. |
Level | String | notice | The alert level.
|
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 detailed event notification information.
- The Details field contains fixed fields and extended fields.
- Fixed fields: specversion, id, source, type, volcpublishtime, volcregion, volcaccountid, volceventbusname, volcresourcename, subject, and time. Fixed fields are displayed even if they are empty.
- Extended fields: Except for fixed fields, all other fields are extended fields. Extended fields are event types defined by cloud products. For information about how to view extended fields, see Obtain detailed information about target events in JSON format.
{
"AccountId": "210035****",
"Description": "Restart instance: Execution successful",
"DescriptionCN": "Restart instance: Execution successful",
"Details": {
"data": {
"EventId": "e-ydzexhbtxv38dekp****",
"EventStatus": "Succeeded",
"EventType": "RebootInstance",
"ExtraInfo": {},
"HappenAt": "2025-07-03T17:00:20+08:00",
"InstanceId": "i-yds68jq22oqc6ili****",
"InstanceName": "cm-data-test",
"PrivateIpAddress": [
"172.xx.xx.2"
],
"PublicIpAddress": [],
"WithGPUDevice": false
},
"datacontenttype": "application/json",
"id": "194069710419630****",
"project": "default",
"resourceid": "i-yds68jq22oqc6ili****",
"source": "ecs",
"specversion": "1.0",
"subject": "ecs:cn-beijing:210035****:instance/i-yds68jq22oqc6ili****",
"time": "2025-07-03T17:00:20+08:00",
"type": "ecs:Instance:RebootInstance.Succeeded",
"volcaccountid": "210035****",
"volceventbusname": "default",
"volcprojectname": "",
"volcpublishtime": "2025-07-03T17:00:20+08:00",
"volcregion": "cn-beijing",
"volcresourcename": "cm-data-test"
},
"EventType": "ecs:Instance:RebootInstance.Succeeded",
"HappenedAt": 1751533220,
"Id": "194069710419630****",
"ProjectName": "default",
"Region": "cn-beijing",
"Rules": [
{
"Level": "critical",
"RuleId": "194069687426716****",
"RuleName": "test_ecs_event"
}
],
"Source": "ecs",
"Type": "Event"
}
Obtain detailed information about target events in JSON format
The extended fields in the message body (event alert) returned by Cloud Monitor mainly originate from the data reported by cloud products when they report events. You can place this data in the data field nested under the Details field, as the callback request body for the event alert.
- Log in to the Cloud Monitor console.
- In the left navigation pane, click "Event Center > Cloud Service Event".
- In the "Actions" column of the target event, click the "Details" button to view detailed information about the event in JSON format.
Last updated: 2025.09.17 10:14:54
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
