Queries blacklist policies.
Debugging
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.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
cms:DescribeMetricRuleBlackList | list |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
Namespace | string | No | The timestamp when the blacklist policy expired. Unit: milliseconds. | acs_ecs_dashboard |
PageNumber | integer | No | The name of the metric. | 1 |
PageSize | integer | No | The categories of the Alibaba Cloud service. For example, ApsaraDB for Redis includes the following categories: ApsaraDB for Redis (standard architecture), ApsaraDB for Redis (cluster architecture), and ApsaraDB for Redis (read/write splitting architecture). In this case, the valid values of this parameter for ApsaraDB for Redis include | 100 |
Order | integer | No | The HTTP status code. Note
The status code 200 indicates that the call was successful.
| DESC |
Category | string | No | The ID of the blacklist policy. | ecs |
Ids | array | No | ||
string | No | The operation that you want to perform. Set the value to DescribeMetricRuleBlackList. | a9ad2ac2-3ed9-11ed-b878-0242ac12**** | |
Name | string | No | The name of the blacklist policy. This parameter supports fuzzy match. | Blacklist-01 |
ScopeType | string | No | The effective scope of the blacklist policy. Valid values:
| USER |
IsEnable | boolean | No | The status of the blacklist policy. Valid values:
| true |
InstanceIds | array | No | The IDs of the instances in the blacklist policy. Valid values of N: 0 to 10. | |
string | No | The ID of the instance in the blacklist policy. | i-2ze2d6j5uhg20x47**** |
Indicates whether the call was successful. Valid values:
- true: The call was successful.
- false: The call failed.
Response parameters
Examples
Sample success responses
JSON
format
{
"Code": "200",
"Message": "The Request is not authorization.",
"RequestId": "D63E76CB-29AA-5B9F-88CE-400A6F28D428",
"Total": 1,
"Success": true,
"DescribeMetricRuleBlackList": [
{
"EffectiveTime": "00:00-23:59",
"UpdateTime": "1665718373000",
"CreateTime": "1665714561000",
"ScopeType": "USER",
"IsEnable": true,
"Namespace": "acs_ecs_dashboard",
"Category": "ecs",
"EnableEndTime": 1640608200000,
"Name": "Blacklist-01",
"EnableStartTime": 1640237400000,
"Id": "93514c96-ceb8-47d8-8ee3-93b6d98b****",
"Metrics": [
{
"Resource": "[{\"device\":\"C:\"}]",
"MetricName": "disk_utilization"
}
],
"Instances": [
"i-rj99xc6cptkk64ml****"
],
"ScopeValue": [
"[\"67****\",\"78****\"]"
]
}
]
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | ParameterInvalid | Illegal parameters. | - |
403 | AccessForbidden | User not authorized to operate on the specified resource. | - |
404 | ResourceNotFound | The specified resource is not found. | The specified resource is not found. |
409 | ResourceConflict | Concurrent modification of resources. | - |
409 | ResourceExist | Resources already exist. | - |
500 | InternalError | The request processing has failed due to some unknown error. | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-07-11 | The Error code has changed. The request parameters of the API has changed | View Change Details |
2022-06-22 | Add Operation | View Change Details |