Help Center/ Relational Database Service_RDS for PostgreSQL/ User Guide/ Instance Management/ Monitoring Dashboard
Updated on 2026-02-13 GMT+08:00
View PDF
Share

Monitoring Dashboard

Cloud Eye monitors operating statuses of DB instances. RDS allows you to view real-time performance metrics and historical metrics of all RDS for PostgreSQL instances under your account. This helps you identify abnormal instances and take actions in a timely manner.

Viewing Real-Time Metrics

On the Dashboard page, select PostgreSQL for Monitoring Dashboards to view the real-time performance metrics of RDS for PostgreSQL instances under your account.
Figure 1 Monitoring list
Table 1 Monitoring parameters

Parameter

Description

Instance Name/ID

Only monitoring data of created DB instances is displayed.

You can click an instance name to go to the Summary page of the instance.

Instance Type

The following types are available:

  • Single-node
  • Primary/Standby
  • Read replica

DB Engine Version

All RDS for PostgreSQL versions can be displayed.

Status

The following statuses are available:

  • Normal: Real-time monitoring data is displayed.
    NOTE:

    The monitoring data and graphics are available for a new instance after the instance runs for about 10 minutes.

  • Abnormal: There is no monitoring data. The default values for all metrics are 0. The monitoring data is available only after the instance becomes normal.
  • Stopped: There is no monitoring data. The default values for all metrics are 0. The monitoring data is available only after the instance is started.

Monitoring Metrics

For details about metric description and handling suggestions for abnormal metrics, see Table 2. The following metrics are available:

  • CPU Usage (%)
  • Memory Usage (%)
  • Storage Usage (%)
  • TPS
  • IOPS
  • Active Connections
  • Slow SQL Statements
Table 2 Monitoring metrics

Metric

Description

Solution

Practices

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

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

Storage 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

TPS

Execution times of submitted and rollback transactions per second
  • Evaluate the SQL execution plan and add indexes to avoid full table scanning.
  • Upgrade vCPU specifications for compute-intensive workloads.

Troubleshooting High CPU Usage

IOPS

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.

Troubleshooting Database Age Increase Problem

Active Connections

Number of active database connections
  • Check whether applications are connected to the instance, optimize the connections, and release unnecessary connections.
  • Upgrade the specifications if needed.

Troubleshooting Abnormal Connections and Active Connections

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

Viewing Historical Metrics

You can select multiple instances from the monitoring list and click View Historical Metrics to view metric trend charts of the instances in the Historical Metrics area.
Figure 2 Historical metrics
  • You can view metric changes of up to 10 instances at a time.
  • The following monitoring time windows are supported: last 1 hour, last 3 hours, last 12 hours, last 24 hours, last 7 days, and a custom time period.
  • For details about monitoring metrics and handling suggestions for abnormal metrics, see Table 2.
  • If the primary/standby replication lag metric is abnormal, see Troubleshooting High Oldest Replication Slot Lag or Replication Lag.
Parent Topic: Instance Management