Obtaining Data of a Single Metric on Multiple Nodes

Function

This API is used to obtain data of 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

POST /v3/{project_id}/multi-nodes/single-metric

**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 allowed. Default Value N/A

Request Parameters

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
metric_name	Yes	String	Definition Metric name Constraints N/A Range Table 4 Default Value N/A
start_at	Yes	Long	Definition Start time Constraints Unix timestamp, in milliseconds Range [0, 2^63 – 1]. The actual value depends on the query result. Default Value N/A
end_at	Yes	Long	Definition End time Constraints Unix timestamp, in milliseconds Range [0, 2^63 – 1]. The actual value depends on the query result. Default Value N/A
instance_infos	Yes	Array of Table 3 objects	Definition Instance information list Constraints N/A

**Table 3** instance_infos
Parameter	Mandatory	Type	Description
datastore_type	Yes	String	Definition Database type Constraints N/A Range MySQL TaurusDB PostgreSQL Microsoft SQL Server Default Value N/A
node_infos	Yes	Array of Table 4 objects	Definition Node list Constraints N/A

**Table 4** node_infos
Parameter	Mandatory	Type	Description
instance_id	Yes	String	Definition Unique ID of an instance. Constraints N/A Range The value can contain 36 characters. Only letters and digits are allowed. Default Value N/A
node_ids	Yes	Array of strings	Definition Unique IDs of nodes. You can obtain the node IDs from the node list in the instance details. The value can contain 36 characters. Only letters and digits are allowed. Constraints Multiple values need to be separated by commas (,).

Response Parameters

Status code: 200

**Table 5** Response body parameters
Parameter	Type	Description
metric_name	String	Definition Metric name Range N/A
unit	String	Definition Unit Range N/A
metrics	Array of Table 6 objects	Definition Metric

**Table 6** metrics
Parameter	Type	Description
instance_id	String	Definition Instance ID, which uniquely identifies an instance. You can obtain the instance ID from the instance list or instance details. Range The value can contain 36 characters. Only letters and digits are allowed.
node_id	String	Definition Unique ID of a node. You can obtain the node ID from the node list in the instance details. Range The value can contain 36 characters. Only letters and digits are allowed.
series	Array of double	Definition Metric
timestamps	Array of long	Definition Timestamp

Example Requests

POST https://das.cn-north-1.myhuaweicloud.com/v3/054e292c9880d4992f02c0196d3ea468/multi-nodes/single-metric
{
   "metric_name": "mem_usage",
   "start_at": 1736402167049,
   "end_at": 1736403967049,
   "instance_infos": [
       {
           "datastore_type": "MySQL",
           "node_infos": [
               {
                   "instance_id": "5c59fa7d6f09456b947f32922f9aeda1in01",
                   "node_ids": [
                       "09ab88b8a12340569ac056af284011d9no01"
                   ]
               }
           ]
       }
   ]
}

Example Responses

Status code: 200

Successful response

{  "metric_name": "mem_usage",
  "unit": "%",
  "metrics": [
    {
      "instance_id": "5c59fa7d6f09456b947f32922f9aeda1in01",
      "node_id": "09ab88b8a12340569ac056af284011d9no01",
      "series": [
        54.2,
        54.18,
        54.13,
        54.1,
        54.13,
        54.15,
        54.2,
        54.17,
        54.13,
        54.18,
        54.17,
        54.27,
        54.15,
        54.1,
        54.2,
        54.2,
        54.22,
        54.17,
        54.15,
        54.17,
        54.18,
        54.17,
        54.2,
        54.18,
        54.23,
        54.17,
        54.13,
        54.1
      ],
      "timestamps": [
        1736402220,
        1736402280,
        1736402340,
        1736402400,
        1736402460,
        1736402520,
        1736402580,
        1736402640,
        1736402700,
        1736402760,
        1736402820,
        1736402880,
        1736402940,
        1736403000,
        1736403060,
        1736403120,
        1736403180,
        1736403240,
        1736403300,
        1736403360,
        1736403420,
        1736403480,
        1736403540,
        1736403600,
        1736403660,
        1736403720,
        1736403780,
        1736403840
      ]
    }
  ]
}

Status Codes

Status Code	Description
200	Successful response
400	Bad request
500	Internal server error

Error Codes

See Error Codes.

Parent topic: Intelligent O&M

Previous topic: Querying Instance Distribution

Next topic: Obtaining Information About a Single Instance Node