When the database proxy for your ApsaraDB RDS for PostgreSQL instance experiences high load or connection issues, reviewing proxy performance metrics helps you decide whether to scale the number of proxy nodes or adjust read weights for read-only instances.
Prerequisites
Before you begin, ensure that you have:
The database proxy feature enabled. For more information, see Enable the database proxy feature.
View proxy monitoring data
Go to the Instances page. In the top navigation bar, select the region where your RDS instance resides. Find the instance and click its ID.
In the left navigation pane, click Database Proxy.
Click View Monitoring Data.
Select a time range to query monitoring data.
Available metrics
The proxy monitoring page displays the following six metrics:
| Metric | Description |
|---|---|
| CPU Utilization (%) | CPU usage of the proxy node. Use this to determine whether the proxy is compute-bound. |
| Current Connections (Counts/s) | Number of active connections to the proxy at a given moment. |
| Connection Rate (Counts/s) | Rate at which new connections are being established to the proxy. |
| Request Rate (Counts/s) | Number of requests processed by the proxy per second. |
| Inbound Traffic (Byte/s) | Data received by the proxy from clients, in bytes per second. |
| Outbound Traffic (B/s) | Data sent by the proxy to clients, in bytes per second. |
Monitoring granularity
The time granularity of data points varies based on the selected query time range:
| Time range | Granularity |
|---|---|
| ≤ 1 hour | 5 seconds |
| > 1 hour and ≤ 2 hours | 10 seconds |
| > 2 hours and ≤ 6 hours | 30 seconds |
| > 6 hours and ≤ 1 day | 2 minutes |
| > 1 day and ≤ 7 days | 30 minutes |
| > 7 days and ≤ 30 days | 1 hour |
API reference
| API | Description |
|---|---|
| DescribeDBProxyPerformance | Queries the performance data of a database proxy. |