You can call this operation to process an anomalous activity.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes ModifyEventStatus

The operation that you want to perform. Set the value to ModifyEventStatus.

DealReason String Yes Anomaly confirmed

The reason of the way in which you process the anomalous activity.

Id Long Yes 12345

The unique ID of the anomalous activity to process.

Note You can call the DescribeEvents operation to query the ID of the anomalous activity.
Status Integer Yes 1

The way in which you want to process the anomalous activity. Valid values:

  • 1: Exclude the anomalous activity as a false positive.
  • 2: Confirm the anomalous activity as an anomaly.
Backed Boolean No true

Specifies whether to use the processing result of the anomalous activity to enhance the detection of anomalous activities. By enhancing the detection, you can improve the detection accuracy and the rate of triggering alerts for anomalous activities. Valid values:

  • true: enhances the detection.
  • false: does not enhance the detection.
Lang String No zh

The language of the request and response. Valid values:

  • zh: Chinese
  • en: English

Response parameters

Parameter Type Example Description
RequestId String 8491DBFD-48C0-4E11-B6FC-6F38921244A9

The ID of the request.

Examples

Sample requests


http(s)://[Endpoint]/? Action=ModifyEventStatus
&<Common request parameters>

Sample success responses

XML format

<ModifyEventStatus>
	  <RequestId>8491DBFD-48C0-4E11-B6FC-6F38921244A9</RequestId>
</ModifyEventStatus>

JSON format

{
	"RequestId":"8491DBFD-48C0-4E11-B6FC-6F38921244A9"
}

Error codes

For a list of error codes, visit the API Error Center.