AWS AmazonRDS documentation change
Summary
Added identical notes to five CloudWatch metrics clarifying they do not include data for PostgreSQL workloads using Extended Protocol.
Security assessment
This is the same documentation update as in the Aurora guide, providing clarification about metric limitations. No security vulnerability, incident, or weakness is mentioned or addressed. The change is purely informational about monitoring scope limitations.
Diff
diff --git a/AmazonRDS/latest/UserGuide/rds-proxy.monitoring.md b/AmazonRDS/latest/UserGuide/rds-proxy.monitoring.md index d070ccb34..1628f56ef 100644 --- a//AmazonRDS/latest/UserGuide/rds-proxy.monitoring.md +++ b//AmazonRDS/latest/UserGuide/rds-proxy.monitoring.md @@ -58,5 +58,5 @@ Metric | Description | Valid period | CloudWatch dimension set -`QueryDatabaseResponseLatency` | The time in microseconds that the database took to respond to the query. The most useful statistic for this metric is `Average`. | 1 minute and above | Dimension set 1, Dimension set 2, Dimension set 3, Dimension set 4 -`QueryRequests` | The number of queries received. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. | 1 minute and above | Dimension set 1, Dimension set 2 -`QueryRequestsNoTLS` | The number of queries received from non-TLS connections. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. | 1 minute and above | Dimension set 1, Dimension set 2 -`QueryRequestsTLS` | The number of queries received from TLS connections. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. | 1 minute and above | Dimension set 1, Dimension set 2 -`QueryResponseLatency` | The time in microseconds between getting a query request and the proxy responding to it. The most useful statistic for this metric is `Average`. | 1 minute and above | Dimension set 1, Dimension set 2 +`QueryDatabaseResponseLatency` | The time in microseconds that the database took to respond to the query. The most useful statistic for this metric is `Average`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2, Dimension set 3, Dimension set 4 +`QueryRequests` | The number of queries received. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2 +`QueryRequestsNoTLS` | The number of queries received from non-TLS connections. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2 +`QueryRequestsTLS` | The number of queries received from TLS connections. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2 +`QueryResponseLatency` | The time in microseconds between getting a query request and the proxy responding to it. The most useful statistic for this metric is `Average`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2