All Products
Search
Document Center

AnalyticDB:DescribeHealthStatus

Last Updated:Aug 28, 2026

Retrieves the health status of an AnalyticDB for PostgreSQL instance and its nodes.

Operation description

This operation is called to query the health status of an AnalyticDB for PostgreSQL instance in elastic storage mode or Serverless mode and its coordinator and compute nodes.

Limits

You can call this operation up to 1,000 times per second per account. If the number of the calls per second exceeds the limit, throttling is triggered. As a result, your business may be affected. We recommend that you take note of the limit when you call this operation.

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

gpdb:DescribeHealthStatus

get

*DBInstance

acs:gpdb:*:{#accountId}:dbinstance/{#DBInstanceId}

None None

Request parameters

Parameter

Type

Required

Description

Example

DBInstanceId

string

Yes

The ID of the instance.

Note

You can call the DescribeDBInstances operation to query the details of all AnalyticDB for PostgreSQL instances in a specific region, including instance IDs.

gp-bp12ga6v69h86****

Key

string

Yes

The performance metric that you want to query. Separate multiple values with commas (,). For more information, see Performance parameters.

node_master_status,node_master_connection_status,node_segment_connection_status,node_segment_disk_status

Response elements

Element

Type

Description

Example

object

Status

object

The queried performance metrics. Each performance metric consists of the parameter name, status, and metric value. The metric information is returned only for the performance parameters specified by Key. For example, if you set Key to adbpg_status, only the metric information of adbpg_status is returned.

For more information about performance parameters, see Performance parameters.

{"node_master_connection_status":{"Status":"healthy","Value":1.6}}

adbpg_status

object

The information of instance health status.

Status

string

The health status of the instance. Valid values:

  • critical: The coordinator node or a compute node is unavailable. In this case, this metric is marked in red in the console.

  • healthy: All nodes are available. In this case, this metric is marked in green in the console.

healthy

Value

number

The metric value of instance health status. Valid values:

  • 1: healthy

  • 0: critical

1

adbpg_connection_status

object

The information of instance connection health status.

Status

string

The connection health status of the instance. Valid values:

  • critical: The instance connection usage is greater than 95%. In this case, this metric is marked in red in the console.

  • warning: The instance connection usage is greater than 90% and less than or equal to 95%. In this case, this metric is marked in yellow in the console.

  • healthy: The instance connection usage is less than or equal to 90%. In this case, this metric is marked in green in the console.

Note

The instance connection usage is the maximum connection usage among all the coordinator and compute nodes.

healthy

Value

number

The metric value of instance connection usage.

Unit: %.

1.71

adbpg_disk_status

object

The information of instance storage status.

Note

This parameter value is returned only for instances in elastic storage mode.

Status

string

The storage status of the instance. Valid values:

  • critical: The instance storage usage is greater than or equal to 90%. In this case, this metric is marked in red in the console and the instance is locked.

  • warning: The instance storage usage is greater than or equal to 70% and less than 90%. In this case, this metric is marked in yellow in the console.

  • healthy: The instance storage usage is less than 70%. In this case, this metric is marked in green in the console.

Note

The instance storage usage is the average storage usage of all compute nodes.

healthy

Value

number

The metric value of instance storage usage.

Unit: %.

1.52

adbpg_disk_usage_percent

object

The information of instance storage usage.

Note

This parameter value is returned only for instances in elastic storage mode.

Status

string

The status corresponding to the storage usage of the instance. Valid values:

  • critical: The instance storage usage is greater than or equal to 90%. In this case, the instance is locked.

  • warning: The instance storage usage is greater than or equal to 70% and less than 90%.

  • healthy: The instance storage usage is less than 70%.

Note

The instance storage usage is the average storage usage of all compute nodes.

healthy

Value

number

The metric value of instance storage usage.

Unit: %.

1.52

adbpg_master_disk_usage_percent_max

object

The information of maximum coordinator node storage usage.

Note

This parameter value is returned only for instances in elastic storage mode.

Status

string

The status corresponding to the maximum storage usage of the coordinator node. Valid values:

  • critical: The coordinator node storage usage is greater than or equal to 90%. In this case, the instance is locked.

  • warning: The coordinator node storage usage is greater than or equal to 70% and less than 90%.

  • healthy: The coordinator node storage usage is less than 70%.

healthy

Value

number

The metric value of maximum coordinator node storage usage.

Unit: %.

1.34

adbgp_segment_disk_usage_percent_max

object

The information of maximum compute node storage usage.

Note

This parameter value is returned only for instances in elastic storage mode.

Status

string

The status corresponding to the maximum storage usage among all compute nodes. Valid values:

  • critical: The compute node storage usage is greater than or equal to 90%. In this case, the instance is locked.

  • warning: The compute node storage usage is greater than or equal to 80% and less than 90%.

  • healthy: The compute node storage usage is less than 80%.

healthy

Value

number

The metric value of maximum compute node storage usage.

Unit: %.

1.52

node_master_status

object

The information of coordinator node health status.

Status

string

The health status of the coordinator node. Valid values:

  • critical: The primary or standby coordinator node is unavailable. In this case, this metric is marked in red in the console.

  • healthy: Both the primary and standby coordinator nodes are available. In this case, this metric is marked in green in the console.

healthy

Value

number

The metric value of coordinator node health status. Valid values:

  • 1: healthy

  • 0: critical

1

node_segment_disk_status

object

The information of compute node storage status.

Note

This parameter value is returned only for instances in elastic storage mode.

Status

string

The storage status of compute nodes. Valid values:

  • critical: The compute node storage usage is greater than or equal to 90%. In this case, this metric is marked in red in the console and the instance is locked.

  • warning: The compute node storage usage is greater than or equal to 80% and less than 90%. In this case, this metric is marked in yellow in the console.

  • healthy: The compute node storage usage is less than 80%. In this case, this metric is marked in green in the console.

Note

The compute node storage usage is the maximum storage usage among all compute nodes.

healthy

Value

number

The metric value of maximum compute node storage usage.

Unit: %.

1.52

node_master_connection_status

object

The information of coordinator node connection health status.

Status

string

The connection health status of the coordinator node. Valid values:

  • critical: The coordinator node connection usage is greater than 95%. In this case, this metric is marked in red in the console.

  • warning: The coordinator node connection usage is greater than or equal to 90% and less than 95%. In this case, this metric is marked in yellow in the console.

  • healthy: The coordinator node connection usage is less than 90%. In this case, this metric is marked in green in the console.

Note

The coordinator node connection usage is the maximum connection usage of the coordinator node.

healthy

Value

number

The metric value of coordinator node connection usage.

Unit: %.

1.71

node_segment_connection_status

object

The information of compute node connection health status.

Status

string

The connection health status of compute nodes. Valid values:

  • critical: The compute node connection usage is greater than or equal to 95%. In this case, this metric is marked in red in the console.

  • warning: The compute node connection usage is greater than or equal to 90% and less than 95%. In this case, this metric is marked in yellow in the console.

  • healthy: The compute node connection usage is less than 90%. In this case, this metric is marked in green in the console.

Note

The compute node connection usage is the maximum connection usage among all compute nodes.

healthy

Value

number

The metric value of maximum compute node connection usage.

Unit: %.

0.48

adbpg_master_status

object

The information of coordinator node availability status.

Status

string

The availability status of the coordinator node. Valid values:

  • critical: Both the primary and standby coordinator nodes are unavailable. In this case, this metric is marked in red in the console.

  • warning: The primary or standby coordinator node is unavailable. In this case, this metric is marked in yellow in the console.

  • healthy: Both the primary and standby coordinator nodes are available. In this case, this metric is marked in green in the console.

healthy

Value

number

The metric value of coordinator node availability status. Valid values:

1

adbpg_segment_status

object

The information of compute node availability status.

Status

string

The availability status of compute nodes. Valid values:

  • critical: All the primary and secondary compute nodes are unavailable. In this case, this metric is marked in red in the console.

  • warning: Fifty percent or more than fifty percent of compute nodes are unavailable. In this case, this metric is marked in yellow in the console.

  • healthy: All compute nodes are available. In this case, this metric is marked in green in the console.

healthy

Value

number

The metric value of compute node availability status.

1

adbpg_instance_total_data_gb

object

The total amount of data storage of the instance.

Value

number

The total amount of data storage of the instance. Unit: GB.

4.1

adbpg_instance_hot_data_gb

object

The total amount of hot data storage.

Value

number

The total amount of hot data storage. Unit: GB.

4.1

adbpg_instance_cold_data_gb

object

The total amount of cold data storage.

Value

number

The total amount of cold data storage. Unit: GB.

0

RequestId

string

The ID of the request.

D97B4191-104D-10CE-8BC5-53**********

DBClusterId

string

The ID of instance.

gp-bp12ga6v69h86****

Examples

Success response

JSON format

{
  "Status": {
    "adbpg_status": {
      "Status": "healthy",
      "Value": 1
    },
    "adbpg_connection_status": {
      "Status": "healthy",
      "Value": 1.71
    },
    "adbpg_disk_status": {
      "Status": "healthy",
      "Value": 1.52
    },
    "adbpg_disk_usage_percent": {
      "Status": "healthy",
      "Value": 1.52
    },
    "adbpg_master_disk_usage_percent_max": {
      "Status": "healthy",
      "Value": 1.34
    },
    "adbgp_segment_disk_usage_percent_max": {
      "Status": "healthy",
      "Value": 1.52
    },
    "node_master_status": {
      "Status": "healthy",
      "Value": 1
    },
    "node_segment_disk_status": {
      "Status": "healthy",
      "Value": 1.52
    },
    "node_master_connection_status": {
      "Status": "healthy",
      "Value": 1.71
    },
    "node_segment_connection_status": {
      "Status": "healthy",
      "Value": 0.48
    },
    "adbpg_master_status": {
      "Status": "healthy",
      "Value": 1
    },
    "adbpg_segment_status": {
      "Status": "healthy",
      "Value": 1
    },
    "adbpg_instance_total_data_gb": {
      "Value": 4.1
    },
    "adbpg_instance_hot_data_gb": {
      "Value": 4.1
    },
    "adbpg_instance_cold_data_gb": {
      "Value": 0
    }
  },
  "RequestId": "D97B4191-104D-10CE-8BC5-53**********",
  "DBClusterId": "gp-bp12ga6v69h86****"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.