By using AWS re:Post, you agree to the Terms of Use
/Fix DatabaseConnectionsCurrentlySessionPinned metric on RDS Proxy dashboard/

Fix DatabaseConnectionsCurrentlySessionPinned metric on RDS Proxy dashboard

0

Currently on the default dashboard for RDS proxy the DatabaseConnectionsCurrentlySessionPinned metric is always empty despite the fact that hundreds of connections are being pinned. After consulting AWS support we were informed that this metric is actually a snapshot which is quite confusing and not useful for users.

The DatabaseConnectionsCurrentlySessionPinned metric in RDS proxy dashboard should be fixed so it actually matches the number of occurrences of connection pinning. We can see the correct metric if we access that via Cloudwatch metrics, the same metric query should be used to populate the default RDS proxy dashboard.

2 Answers
0

Hi Andre de Camargo

I understand that on the default dashboard for RDS proxy the DatabaseConnectionsCurrentlySessionPinned metric is always empty despite the fact that hundreds of connections are being pinned. After consulting AWS support we were informed that this metric is actually a snapshot which is quite confusing and not useful for users. Please correct me if my understanding is wrong.

The above metrics is a direct result of Dimension set. You can use the following commands to verify that all components of the connection mechanism can communicate with the other components. Examine the proxy itself using the describe-db-proxies command. Also examine the associated target group using the describe-db-proxy-target-groups Check that the details of the targets match the RDS DB instance or Aurora DB cluster that you intend to associate with the proxy[1].

Use the following commands. aws rds describe-db-proxies --db-proxy-name $DB_PROXY_NAME aws rds describe-db-proxy-target-groups --db-proxy-name $DB_PROXY_NAME

You can change certain settings associated with a proxy after you create the proxy. You do so by modifying the proxy itself, its associated target group, or both. Each proxy has an associated target group[2].

I hope the above information is helpful.

References:

1.https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy.troubleshooting.html#rds-proxy-verifying 2.https://docs.amazonaws.cn/en_us/AmazonRDS/latest/UserGuide/rds-proxy-managing.html#rds-proxy-modifying-proxy

answered 19 days ago
0

Hi

Seems like CloudWatch console you can see the metrics but not from the RDS console. I would suggest raise a feature request or bug report request from the RDS console lower left corner Feedback button.

Seems like you also have support plan available, you may raise the same concern through support case as well.

As this metrics is a periodic snapshots, using the RDS proxy log to search "The client session was pinned to the database connection" can be another method of seeing the actual pined sessions.

SUPPORT ENGINEER
answered 9 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions