All Products
Search
Document Center

Security Center:OperationCancelIgnoreSuspEvent

Last Updated:Feb 20, 2024

Cancels ignoring alert events.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
yundun-sas:OperationCancelIgnoreSuspEventWrite
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
SecurityEventIdsarrayYes

The IDs of alert events.

longYes

The ID of the alert event.

Note You can call the DescribeSuspEvents operation to query the IDs of alert events.
611689
RemarkstringNo

The remarks.

remark text

Response parameters

ParameterTypeDescriptionExample
object

BaseResult

Successboolean

The handling result of an exception. Valid values:

  • true: successful
  • false: failed
true
Codestring

The status code returned. The status code 200 indicates that the request was is successful. Other status codes indicate that the request fails. You can identify the cause of the failure based on the status code.

200
Messagestring

The error message returned.

successful
RequestIdstring

The request ID.

CE500770-42D3-442E-9DDD-156E0F9F3B45
HttpStatusCodeinteger

The HTTP status code.

200
TimeCostlong

The time consumed for the request. Unit: seconds.

1

Examples

Sample success responses

JSONformat

{
  "Success": true,
  "Code": "200",
  "Message": "successful",
  "RequestId": "CE500770-42D3-442E-9DDD-156E0F9F3B45",
  "HttpStatusCode": 200,
  "TimeCost": 1
}

Error codes

HTTP status codeError codeError messageDescription
400OperationTaskNotExistsThe specified operation task does not exist-
400IllegalParamIllegal param-
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500ServerErrorServerError-

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2023-06-07The Error code has changed. The request parameters of the API has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
Input ParametersThe request parameters of the API has changed.
    Added Input Parameters: Remark
2022-08-01The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
2022-08-01The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400