Updated on 2026-08-25 GMT+08:00

Querying a Single Metric on Multiple Nodes

Function

This API is used to query a single metric on multiple nodes.

Authorization Information

Each account has permissions to call all APIs, but IAM users must have the required permissions specifically assigned.

If you are using role/policy-based authorization, see the required permissions in Permissions Policies and Supported Actions.
If you are using identity policy-based authorization, the following identity policy-based permissions are required.

Action

Access Level

Resource Type (*: required)

Condition Key

Alias

Dependencies

das::showCloudDBAInfo

Read

-

-

-

-

Action	Access Level	Resource Type (*: required)	Condition Key	Alias	Dependencies
das::showCloudDBAInfo	Read	-	-	-	-

URI

GET /v3/{project_id}/metric-names/support

**Table 1** URI parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Definition Project ID of a tenant in a region. To obtain this value, see Obtaining a Project ID. Constraints N/A Range The value can contain 32 characters. Only letters and digits are supported. Default Value N/A

Request Parameters

None

Response Parameters

Status code: 200

**Table 2** Response body parameters
Parameter	Type	Description
support_metric_names	Array of Table 3 objects	Definition Supported metric names

**Table 3** support_metric_names
Parameter	Type	Description
datastore_type	Array of strings	Definition Database type
metric_name	String	Definition Metric name Range N/A
unit	String	Definition Unit Range N/A
description	String	Definition Description Range N/A

Example Requests

GET https://das.cn-north-1.myhuaweicloud.com/v3/054e292c9880d4992f02c0196d3ea468/metric-names/support

Example Responses

Status code: 200

Success.

{
  "support_metric_names": [
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "slow_queries",
      "unit": "count/min",
      "description": "Number of slow SQL statements"
    },
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "mem_usage",
      "unit": "%",
      "description": "memory usage"
    },
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "conn_active_count",
      "unit": "count",
      "description": "Number of active connections"
    },
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "disk_usage",
      "unit": "%",
      "description": "Disk Usage"
    },
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "conn_count",
      "unit": "count",
      "description": "Total Connections"
    },
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "data_disk_used_size",
      "unit": "GB",
      "description": "Disk Usage Size"
    },
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "cpu_usage",
      "unit": "%",
      "description": "CPU usage"
    },
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "binlog_usage",
      "unit": "%",
      "description": "Binlog disk usage"
    },
    {
      "datastore_type": [
        "MySQL"
      ],
      "metric_name": "replication_delay",
      "unit": "s",
      "description": "Replication latency"
    }
  ]
}

Status Codes

Status Code	Description
200	Success.
400	Client error
500	Server error

Error Codes

See Error Codes.

Parent topic: Intelligent O&M