QueryQuotaMetric-阿里云帮助中心

Queries time-series information about quota resource consumption.

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

odps:QueryQuotaMetric

list

*Quota

acs:odps:{#regionId}:{#accountId}:quota/{#metric}

None

Request syntax

POST /api/v1/observations/quota/{metric} HTTP/1.1

Path Parameters

Parameter	Type	Required	Description	Example
metric	string	Yes	The name of the observed metric. Valid values: cpu and memory.	cpu

Request parameters

Parameter	Type	Required	Description	Example
startTime	integer	Yes	The start time of the query time range. The value is a UNIX timestamp in seconds.	1735534322
endTime	integer	Yes	The end time of the query time range. The value is a UNIX timestamp in seconds.	1735536322
strategy	string	No	The data aggregation policy. Default value: max. Valid values: max and avg. Data is collected every 1 minute. If the query time range is large, the adaptive step size for data display exceeds 1 minute, and the metrics are aggregated. This parameter specifies the data aggregation logic.	max
body	object	No	The request body parameters.
nickname	string	No	The nickname of the level-1 quota. This parameter is required.	os_sns_p
subQuotaNickname	string	No	The nickname of the level-2 quota.	os_sns
interval	integer	No	The fixed interval in seconds. By default, this parameter is empty, which indicates that the adaptive interval policy of the system is used. Adaptive interval policy: The interval is 60 seconds if the query time range is within 6 hours, 300 seconds if within 24 hours, 900 seconds if within 72 hours, and 1800 seconds if exceeding 72 hours. Specified interval: Only 60, 300, and 900 are supported. The query time range must be within 72 hours.	60
subMetric	string	No

Response elements

Element	Type	Description	Example
	object	PopResult
requestId	string	The request ID.	0b87b7b316643495896551555e855b
httpCode	integer	The HTTP status code. 1xx: Informational. The request was received and is being processed. 2xx: Success. The request was successfully received, understood, and accepted by the server. 3xx: Redirection. The request was redirected, and further action is required to complete it. 4xx: Client error. The request contains bad syntax, invalid parameters, or cannot be fulfilled. 5xx: Server error. The server failed to fulfill the request due to other reasons.	200
errorCode	string	The error code.	success
errorMsg	string	The error message.	plan \"***\" does not exist
data	object	The returned data.
category	string	Not supported.	Not supported
name	string	The name of the observed metric.	cpu
period	integer	The step size of the monitoring data.	60
metrics	array<object>	The metric values.
	array<object>	The metric values.
metric	object	The metric metadata information.
	string	The metric metadata information. unit: The metadata unit. If the metric is cpu, the unit is Core. If the metric is memory, the unit is GB. type: The metadata type. If the queried metric category is cpu, the metadata types include totalMaxCpu, totalUsedCpu, adhocCpu, adhocUsedCpu, maxCpu, minCpu, requestCpu, usedCpu, elasticMaxCpu, and elasticUsedCpu. If the queried metric category is memory, the metadata types include totalMaxMem, totalUsedMem, adhocMem, adhocUsedMem, elasticMaxMem, elasticUsedMem, maxMem, minMem, and usedMem.	totalUsedCpu
values	array	The time-series data.
	array	The length is 2. The elements are the timestamp and the value.
	number	The length is 2. The elements are the timestamp and the value.	[1757571840,10]

Examples

Success response

JSON format

{
  "requestId": "0b87b7b316643495896551555e855b",
  "httpCode": 200,
  "errorCode": "success",
  "errorMsg": "plan \\\"***\\\" does not exist",
  "data": {
    "category": "Not supported",
    "name": "cpu",
    "period": 60,
    "metrics": [
      {
        "metric": {
          "key": "totalUsedCpu"
        },
        "values": [
          [
            0
          ]
        ]
      }
    ]
  }
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.