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

get

*All Resource

*

None

Request syntax

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

Request parameters

Parameter	Type	Required	Description	Example
cluster	string	No	The cluster ID.	2ijff4be-bf24-4070-89ca-c47c879b0g32
instance	string	No	The instance ID.	i-wz9d00ut2ska3mlyhn6j
pod	string	No	The pod name.	test-pod
namespace	string	No	The namespace of the pod.	default
start	number	No	The start time.	1725797727754
end	number	No	The end time.	1725801327754
showPod	integer	No	Specifies whether to display abnormal events of the pod. Valid values: 不展示 : 0 展示 : 1	1
level	string	No	The severity level of the abnormal event. Valid values: warning : warning error : error potential : potential	potential

Response elements

Element	Type	Description	Example
	object	Schema of Response
code	string	The response code.	Success
data	array<object>	The returned data.
	object	The returned data.
eventList	array	The list of abnormal events.
	string	The name of the abnormal event.	Node root filesystem usage detection
type	string	The type of the abnormality. Valid values: "potential" : potential "error" : error "warning" : warning	health
value	integer	The number of abnormalities of this type.	1
message	string	The business error message. This parameter is not empty when success is false.	result: code=1 msg=(Request failed, status_code != 200)

Examples

Success response

JSON format

{
  "code": "Success",
  "data": [
    {
      "eventList": [
        "Node root filesystem usage detection"
      ],
      "type": "health",
      "value": 1
    }
  ],
  "message": "result: code=1 msg=(Request failed, status_code != 200)"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.