UpdateEventsAttention - Alibaba Cloud Linux - Alibaba Cloud Documentation Center

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

sysom:UpdateEventsAttention

update

*All Resource

*

None

Request syntax

POST /api/v1/openapi/proxy/post/cluster_update_events_attention HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
body	object	No	The request body.
mode	integer	No	The sensitivity of the anomaly event. Valid values: -1 to 3. A value of -1 indicates that the sensitivity is decreased by 1. A value of 0 indicates that the sensitivity is increased by 1. Valid values: 0 : 0 1 : 1 2 : 2 3 : 3 -1 : -1	-1
range	string	No	The scope in which the update takes effect. Valid values: cluster and node. Valid values: node : node cluster : cluster	cluster
uuid	string	Yes	The UUID of the anomaly event.	03de78af-f49f-433d-b5b1-0f6a70c493ba

Response elements

Element	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID, which can be used for end-to-end diagnostics.	44841312-7227-55C9-AE03-D59729BFAE38
code	string	The status code. `code == Success` indicates that the authorization is successful. Other status codes indicate that the authorization failed. Check the `message` field for the detailed fault information.	Success
data	object	The returned data.
mode	integer	The updated attention level value.	1
message	string	The error message.	Instance not belong to current user

Examples

Success response

JSON format

{
  "RequestId": "44841312-7227-55C9-AE03-D59729BFAE38",
  "code": "Success",
  "data": {
    "mode": 1
  },
  "message": "Instance not belong to current user"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.