# Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor-133438.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:04Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [insights](<https://devfeed.tech/tags/insights.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [regression](<https://devfeed.tech/tags/regression.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

## AI overview

CloudWatch metrics can show that RDS Proxy multiplexing has degraded, but enhanced proxy logs help explain why and which connections are involved. CloudWatch Logs Insights queries summarize backend connection borrows, releases, and pins, or trace one connection's lifecycle. For user and ApplicationName attribution, the post correlates proxy TCP events with PostgreSQL connection logs using IP:port; this is a best-effort match that depends on a narrow time window and synchronized timestamps. Healthy multiplexing shows many borrows and releases per backend connection, few pins, and substantially fewer backend than client connections. The post recommends alarms for sustained pinning and an elevated backend-to-client connection ratio, with workload-specific baselines and a traffic floor. Enhanced logging produces detailed SQL text, adds log volume, cost, and possible proxy overhead, so restrict log access, use it temporarily, and disable it after diagnosis.

## Source excerpt

Metrics alone can't always pinpoint what is reducing RDS Proxy multiplexing for PostgreSQL. Part 2 shows how to use Amazon CloudWatch Logs Insights with enhanced proxy logs to find the root cause, what healthy multiplexing looks like in metrics and logs, and how to set up CloudWatch alarms that catch regression.