All Products
Search
Document Center

ApsaraDB RDS:DescribeAvailableMetrics

Last Updated:Nov 11, 2024

Queries all Enhanced Monitoring metrics that are supported by an ApsaraDB RDS for PostgreSQL instance.

Operation description

Supported database engines

  • PostgreSQL

References

Note Before you call this operation, carefully read the following documentation. Make sure that you fully understand the prerequisites and impacts for calling this operation.

View the Enhanced Monitoring metrics

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

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.
OperationAccess levelResource typeCondition keyAssociated operation
rds:DescribeAvailableMetricsget
  • DBInstance
    acs:rds:{#regionId}:{#accountId}:dbinstance/{#dbinstanceId}
  • rds:ResourceTag
none

Request parameters

ParameterTypeRequiredDescriptionExample
DBInstanceNamestringYes

The instance ID. You can call the DescribeDBInstances operation to query the instance ID.

pgm-bp1s1j103lo6****
ResourceGroupIdstringNo

The resource group ID.

rg-acfmy*****

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

TotalRecordCountinteger

The total number of enhanced monitoring metrics that are available for the instance.

4
RequestIdstring

The ID of the request.

5CD61041-35F7-10F7-BE94-33A48B221218
Itemsarray<object>

Details of the Enhanced Monitoring metric.

Metricsobject
GroupKeystring

The key of the group to which the Enhanced Monitoring metric belongs.

os.cpu_usage
SortRuleinteger

The serial number of the Enhanced Monitoring metric.

1
Descriptionstring

The description of the Enhanced Monitoring metric.

OS CPU utilization, equal to the number of OS-consumed CPUs divided by the total number of CPUs
Unitstring

The unit of the Enhanced Monitoring metric.

%
MetricsKeystring

The key of the Enhanced Monitoring metric.

os.cpu_usage.sys.avg
GroupKeyTypestring

The name of the group to which the Enhanced Monitoring metric belongs.

CPU Utilization Rate
MetricsKeyAliasstring

The alias of the Enhanced Monitoring metric.

cpu_sys_per_core
Methodstring

The method that is used to aggregate the monitoring data of the Enhanced Monitoring metric. Valid values:

  • avg: The system calculates the average value of the Enhanced Monitoring metric.
  • min: The system calculates the minimum value of the Enhanced Monitoring metric.
  • max: The system calculates the maximum value of the Enhanced Monitoring metric.
avg
Dimensionstring

The category of the Enhanced Monitoring metric. Valid values:

  • os: OS metric
  • db: database metric
os
DBInstanceNamestring

The instance ID.

rm-bp1*****

Examples

Sample success responses

JSONformat

{
  "TotalRecordCount": 4,
  "RequestId": "5CD61041-35F7-10F7-BE94-33A48B221218",
  "Items": [
    {
      "GroupKey": "os.cpu_usage",
      "SortRule": 1,
      "Description": "OS CPU utilization, equal to the number of OS-consumed CPUs divided by the total number of CPUs\n",
      "Unit": "%",
      "MetricsKey": "os.cpu_usage.sys.avg",
      "GroupKeyType": "CPU Utilization Rate\n",
      "MetricsKeyAlias": "cpu_sys_per_core",
      "Method": "avg",
      "Dimension": "os"
    }
  ],
  "DBInstanceName": "rm-bp1*****"
}

Error codes

HTTP status codeError codeError messageDescription
400InvalidDBInstanceEngineType.Formatthe DB instance engine type does not support this operation.This operation is not supported for the database engine of the instance.
404InvalidDBInstanceName.NotFoundThe database instance does not exist.The name of the RDS instance cannot be found. Check the name of the RDS instance.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2022-08-04The Error code has changed. The request parameters of the API has changed. The response structure of the API has changedView Change Details