ListAbnormalyEvents - Alibaba Cloud Linux - Alibaba Cloud Documentation Center

Retrieves anomaly event information for a cluster, node, or pod within a specified time range.

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:ListAbnormalyEvents

list

*All Resource

*

None

Request syntax

GET /api/v1/openapi/cluster_health/range/abnormaly_events HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
cluster	string	No	The cluster ID.	2d33d4be-bf54-4070-82ca-c1dc2d8b1562
instance	string	No	The instance ID.	i-wz9d00ut2ska3mlyhn6j
start	number	No	The start time.	1725797727754
pod	string	No	The pod name.	test-pod
namespace	string	No	The namespace of the pod.	default
end	number	No	The end time.	1725801327754
level	string	No	The level of the anomaly event. Valid values: warning : warning error : error potential : potential	potential
showPod	integer	No	Specifies whether to display anomaly events of the pod. Valid values: 0 : 0	1
current	integer	No	The current page number. This field exists when pagination is used.	1
pageSize	integer	No	The number of entries per page. Default value: 5. Valid values: 1 to 100.	10
event	string	No	The name of the anomaly event.	Node root filesystem usage check

Response elements

Element	Type	Description	Example
	object	Schema of Response
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	array<object>	The returned result.
	array<object>	The returned data.
created_at	integer	The creation time.	1725801090000
description	string	The description of the anomaly item.	An OOM event occurred on the node. Check the cause of the OOM event
diag_status	integer	The diagnostic status. Valid values: 1: the diagnosis is ready. 2: the diagnosis is running. 3: the diagnosis is complete. 4: the item is not diagnosable. 5: the diagnosis failed. Valid values: 不可诊断 : 4 诊断完成 : 3 诊断失败 : 5 诊断运行中 : 2 诊断已就绪 : 1	3
end_at	integer	The end time of the anomaly event.	1725797727754
instance	string	The instance ID.	i-wz9d00ut2ska3mlyhn6j
item	string	The name of the anomaly item.	Node CPU usage check
level	string	The level of the anomaly item. Valid values: warning : warning error : error potential : potential	potential
namespace	string	The namespace of the pod.	default
opts	array<object>	The list of operations for the anomaly item.
	array<object>	The operation item for the anomaly item.
label	string	The operation type.	diagnose
result	object	The diagnostic result of the anomaly item.
status	string	The diagnostic status.	success
url	string	The URL of the diagnostic details.	/diagnose/result/PhfFg456
type	string	The diagnostic type.	auto
pod	string	The pod name.	test-pod
raw_metrics	object	The raw metrics.
end_time	number	The end time.	1761814928
metrics	array	The list of metric values.
	string	The metric name.	sys_cpu_total
start_time	number	The start time.	1761814928
region_id	string	The region ID.	cn-shanghai
type	string	The type of the anomaly item. Valid values: saturation : saturation load : load latency : latency error : error	saturation
uuid	string	The UUID of the anomaly event.	43f05b46-1034-42e8-a528-6e5ca1108277
message	string	The error code description. This field is empty if no error occurs.	Success
total	integer	The total number of records.	4

Examples

Success response

JSON format

{
  "code": "Success",
  "data": [
    {
      "created_at": 1725801090000,
      "description": "节点发生OOM, 可查看OOM发生原因",
      "diag_status": 3,
      "end_at": 1725797727754,
      "instance": "i-wz9d00ut2ska3mlyhn6j",
      "item": "节点CPU使用率检测",
      "level": "potential",
      "namespace": "default",
      "opts": [
        {
          "label": "diagnose",
          "result": {
            "status": "success",
            "url": "/diagnose/result/PhfFg456"
          },
          "type": "auto"
        }
      ],
      "pod": "test-pod",
      "raw_metrics": {
        "end_time": 1761814928,
        "metrics": [
          "sys_cpu_total"
        ],
        "start_time": 1761814928
      },
      "region_id": "cn-shanghai",
      "type": "saturation",
      "uuid": "43f05b46-1034-42e8-a528-6e5ca1108277"
    }
  ],
  "message": "Success",
  "total": 4
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.