Handles an anomalous event.
Operation description
You can call this operation to handle anomalous events that involve data leaks. This helps protect your data assets at the earliest opportunity.
Limits
You can call this operation up to 10 times per second per account. If the number of the calls per second exceeds the limit, throttling is triggered. As a result, your business may be affected. We recommend that you take note of the limit when you call this operation.
Debugging
Authorization information
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
Lang | string | No | The language of the content within the request and response. Default value: zh_cn. Valid values:
| zh_cn |
Id | long | Yes | The ID of the anomalous event. Note
You can call the DescribeEvents operation to query the ID of the anomalous event.
| 12345 |
Backed | boolean | No | Specifies whether to enhance the detection of anomalous events. If you enhance the detection of anomalous events, the detection accuracy and the rate of triggering alerts for anomalous events are improved. Valid values:
| true |
DealReason | string | No | The reason why the anomalous event is handled. | Anomaly confirmed |
Status | integer | Yes | The method to handle the anomalous event. Valid values:
| 1 |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "8491DBFD-48C0-4E11-B6FC-6F38921244A9"
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|