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

Instance Summary

On the Summary page, you can get knowledge of the overall status of your RDS for PostgreSQL instance, including active alarms, anomalies, and key performance metrics. Intelligent anomaly diagnosis uses operational data analytics and intelligent algorithms to assess instance health, and provides you with solutions and suggestions for handling detected anomalies.

Functions

Table 1 lists the functions provided on the Summary page.

**Table 1** Function description
Function	Description
Instance Information	Shows basic information about your instance and allows you to modify the instance. Basic Information This area displays the DB instance name/ID, description, AZ, and enterprise project, and allows you to configure a maintenance window, reset the root password, and configure a failover priority. Configurations This area displays the DB engine version, and allows you to switch between the primary and standby nodes, change the instance class, scale up storage, and configure replication mode. Connectivity This area displays the VPC, subnet, and recommended maximum connections, and allows you to change the floating IP address, change the private domain name, change the database port, and manage security groups. Billing This area displays the creation time and allows you to change the billing mode.
Alarms	Shows the active alarms of your instance, including alarms in the Alarm (metric) or Triggered (event) state.
Intelligent Anomaly Diagnosis	Shows the health status of your instance based on operational data analysis and intelligent algorithms.
Performance Monitoring	Shows the instance's key performance metrics, including the CPU usage, memory usage, number of SQL statements executed for more than 3s, and number of connections.
Storage & Backup	Shows the storage space and backup space usage of your instance, and allows you to scale up the storage.

Instance Summary

Log in to the RDS console.
Click in the upper left corner and select a region.
On the Instances page, click the target instance name to go to the Summary page.
In the Instance Information area, check the instance information and modify the instance as required.

Figure 1 Instance Information

In the Alarms area, check alarm information of your instance.

Based on the configured alarm rules, you can see active alarms of your instance, including alarms in the Alarm (metric) or Triggered (event) state.

Figure 2 Alarms

To check all alarm records, click All Alarms to go to the Cloud Eye console.
To configure alarm rules, click Alarm Settings to go to the Cloud Eye console.
To check alarms over time, select a time window in the upper part of the Alarms area.
The time window can be the last 1 hour, last 6 hours, last 12 hours, last 24 hours, last 7 days, last 30 days, or a custom time period.

In the Intelligent Anomaly Diagnosis area, view the health diagnosis results of your instance in real time.

Intelligent Anomaly Diagnosis checks instance health using instance operation data and intelligent algorithms and provides diagnosis results and suggestions.

Figure 3 Intelligent Anomaly Diagnosis

Table 2 provides the supported diagnosis items and handling suggestions.

**Table 2** Anomaly description
Diagnosis Item	Metric	Metric Description	Handling Suggestions	Practices
Memory bottleneck	Memory Usage (%)	Memory usage of the monitored object	Upgrade instance specifications. Optimize SQL statements to reduce the use of temporary tables. Reconnect sessions at a specific interval to release memory of the sessions.	Troubleshooting High Memory Usage
Memory bottleneck	Active Connections(Count)	Number of active connections to the current DB instance		Troubleshooting High Memory Usage
High-frequency slow SQL	Slow SQL Statements	Number of slow SQL statements that exceed the specified duration	Optimize slow SQL statements based on the execution plan. Upgrade vCPU specifications for compute-intensive workloads.	Troubleshooting SQL Statements That Have Been Executed for 3s or 5s
Connection bottleneck	Active Connections(Count)	Number of active connections to the current DB instance	Check the application connections and release unnecessary connections. Check the specifications and scale them up if needed.	Troubleshooting Abnormal Connections and Active Connections
Database too old	Maximum Database Age(Count)	Maximum age of the current database, which is the value of max(age(datfrozenxid)) in the pg_database table	Verify that the autovacuum parameter is set to on. If the database age increases due to temporary tables, release client connections to clean up the temporary tables and reclaim resources. If the database age increases due to long-running transactions, cancel the transactions and then run VACUUM on the oldest table in the database.	Troubleshooting Database Age Increase Problem
Capacity bottleneck	Storage Space Usage (%)	Storage space usage of the monitored object	Scaling up storage space: You can configure storage autoscaling. When the storage usage reaches the threshold, autoscaling is triggered. Reducing disk data: Delete useless historical data. If temporary files generated by sorting queries occupy too much storage space, optimize your SQL query statements.	Troubleshooting High Storage Space Usage
	Used Storage Space (GiB)	Used storage space of the monitored object
	Total Storage Space (GiB)	Total storage space of the monitored object
Storage bottleneck	IOPS(count/s)	Average number of I/O requests processed by the system in a specified period	Upgrade instance specifications. To reduce data reads from the disk, optimize the application to make it read data from the buffer first.	How Do I Set an Upper Limit for the Storage Occupied by Temporary Files of My RDS for PostgreSQL Instance?
	Disk Read Throughput (Bytes/s)	Number of bytes read from the disk per second
	Disk Write Throughput (Bytes/s)	Number of bytes written into the disk per second
Lock wait and long transaction	Sessions Waiting for Locks(Count)	Number of sessions that are currently blocked	For long-running transactions, terminate them after confirmation.	Troubleshooting Long-Running Transactions
	Oldest Active Transaction Duration(ms)	Length of time since the start of the transaction that has been active longer than any other current transaction
	Oldest Two-Phase Commit Transaction Duration(ms)	Length of time that has elapsed since the start of the transaction that has been prepared for two-phase commit longer than any other current transaction
High vCPU utilization	CPU Usage (%)	CPU usage of the monitored object	Evaluate the SQL execution plan and add indexes to avoid full table scanning. Upgrade vCPU specifications for compute-intensive workloads.	Troubleshooting High CPU Usage
High vCPU utilization	TPS (Times/s)	Execution times of submitted and rollback transactions per second		Troubleshooting High CPU Usage

In the Performance Monitoring area, you can view the vCPUs (used/total), memory (used/total), number of SQL statements executed for more than 3s, and connection count of your instance.

Figure 4 Performance Monitoring

To check all metrics, click Real-Time Monitoring to go to the DBA Assistant page. For details, see Viewing Performance Metrics of a DB Instance.
To check the analysis results of slow queries, click Slow SQL Log to go to the DBA Assistant page. For details, see Viewing Slow Query Logs of a DB Instance.
To check metric changes over time, select a time range in the upper part.
The time window can be the last 1 hour, last 3 hours, last 12 hours, last 24 hours, last 7 days, last 30 days, or a custom time period.

In the Storage & Backup area, you can check the storage space usage and backup space usage of your instance, enable disk encryption, and scale up storage space.

Figure 5 Storage & Backup

Files that occupy the storage space include data files, log files, and other temporary files. To check the distribution and changes of used storage, see Managing Storage Capacity.
To enable or modify disk encryption after an instance is purchased, refer to Configuring Disk Encryption.
If you enable disk encryption when purchasing an instance, the new storage space after scale-up still uses the original encryption key. Keep the key secure. Once the key is disabled, deleted, or frozen, your instance will become inaccessible.
As workload data increases, the storage capacity of your instance may be insufficient. To scale up the storage space, see Scaling Storage Space.
Backups are stored as packages in OBS and occupy the backup space. If the free space RDS provides is used up, the additional space required will be billed. For the billing details, see How Are RDS Backups Billed?

Parent Topic: Instance Modifications

Instance Summary

Functions

Instance Summary

What is your overall rating for this page?