The monitoring dashboard lets you select specific RDS instances and metrics to monitor, then view and compare their performance trends side by side. Use it to get a consolidated view of instance health and diagnose issues across multiple databases at once.
Prerequisites
Before you begin, make sure that:
-
Your RDS instance runs RDS High-availability Edition
-
Database Autonomy Service (DAS) has enabled the monitoring dashboard feature for your ApsaraDB RDS for PostgreSQL instance (available from May 20, 2022)
Create a monitoring dashboard
-
Log on to the ApsaraDB RDS console.
-
In the left-side navigation pane, choose Maintenance & Monitoring > Performance Monitoring.
-
On the Performance Monitoring page, click the Monitoring Dashboard tab.
-
On the PostgreSQL tab, click Add Monitoring Dashboard.
-
Enter a name in the Dashboard Name field and click OK.
-
Click Select Instances and Metrics, select the instances and metrics you want to monitor, then click the
icon.You can select up to 32 RDS instances at a time. For details about available metrics, see Metrics.
-
Click Confirm.
To modify the instances or metrics in a dashboard, click Add Instances and Metrics.
View metric trends
-
Log on to the ApsaraDB RDS console.
-
In the left-side navigation pane, choose Maintenance & Monitoring > Performance Monitoring.
-
On the Performance Monitoring page, click the Monitoring Dashboard tab.
-
Click the database engine tab, select the dashboard you want to view, then set a time range to display trend charts for that period.
The end time must be later than the start time, and the selected range cannot exceed seven days.
The dashboard provides the following controls:
| Control | Description |
|---|---|
| Instance filtering | Filter by instance to view and compare metrics across multiple RDS instances. |
| Auto Refresh (Every 5 Seconds) | Toggle on to refresh all trend charts every 5 seconds. |
| Linkage Chart | Toggle on to view metric values at the same point in time across charts. |
| Chart Layout | Set the number of trend charts displayed per row. |
| Add Instances and Metrics | Modify the instances or metrics included in the dashboard. |
| Details (in a chart) | Expand the chart and adjust its time range independently. |
| Delete (in a chart) | Remove the chart from the dashboard. |
Click theicon next to a metric name on the dashboard to view its description.
Metrics
Host metrics
| Parameter | Description |
|---|---|
cpu_sys_ratio |
CPU utilization of the PostgreSQL process in the kernel state |
cpu_user_ratio |
CPU utilization of the PostgreSQL process in the user state |
cpu_usage |
CPU utilization of the PostgreSQL process |
mem_usage |
Memory usage of the PostgreSQL process |
data.r_s |
Read IOPS of the disk on which the data directory resides |
data.iops |
IOPS of the disk on which the data directory resides |
data.w_s |
Write IOPS of the disk on which the data directory resides |
local_fs_size_total |
Total disk space of the server |
data.fs.used |
Used disk space on the data directory disk |
data.fs.usage |
Disk space usage of the data directory disk |
network_out_io |
Outbound network traffic of the PostgreSQL process |
network_io |
Network traffic of the PostgreSQL process |
network_in_io |
Inbound network traffic of the PostgreSQL process |
Connections
| Parameter | Description |
|---|---|
waiting_connection |
Number of pending connections |
idle_in_transaction |
Number of idle sessions |
active_session |
Number of active connections |
total_session |
Total number of current connections |
Throughput
| Parameter | Description |
|---|---|
tup_inserted |
Records inserted per second |
tup_deleted |
Records deleted per second |
tup_updated |
Records updated per second |
tup_returned |
Records returned per second for full table scans |
tup_fetched |
Records returned per second for index scans |
Transactions
| Parameter | Description |
|---|---|
tps |
Transactions per second (TPS) |
xact_rollback |
Transactions rolled back per second |
xact_commit |
Transactions committed per second |
deadlocks |
Deadlocks per second |
oldest_snapshot |
The point in time before which dead tuples can be recycled by the instance |
Replication
| Parameter | Description |
|---|---|
max_sent_delay |
Data replication latency from the secondary RDS instance |
max_replay_delay |
Latency at which the secondary RDS instance replays transaction commits |
Slow queries and long-running transactions
| Parameter | Description |
|---|---|
long_query_1s |
SQL statements with execution duration >= 1 second |
long_query_3s |
SQL statements with execution duration >= 3 seconds |
long_query_5s |
SQL statements with execution duration >= 5 seconds |
long_idle_in_transaction_1s |
Transactions idle for 1 second or longer |
long_idle_in_transaction_3s |
Transactions idle for 3 seconds or longer |
long_idle_in_transaction_5s |
Transactions idle for 5 seconds or longer |
long_2pc_1s |
2PC transactions lasting 1 second or longer |
long_2pc_3s |
2PC transactions lasting 3 seconds or longer |
long_2pc_5s |
2PC transactions lasting 5 seconds or longer |