Enabling Hikari Connection Pool Monitoring

Hi all,

TLDR

We need your help to enable Hikari-connection-pool monitoring, guide is at: https://29022131.atlassian.net/wiki/spaces/DAT/pages/1347455945/How+to+Monitor+Hikari+Connection+Pool.
And also please follow our recommendation (if you haven't done it) at https://tvlk.slack.com/files/T02T3CAFM/F012KUU2RS5.

Please do them before 30 April 2020 23.59.59 GMT+7.

Why?

By tuning the connection pool size, we can have more accurate metrics to decide RDS sizing. Because each connection to database will consume resources in PostgreSQL instances, even if the connection is idle. Currently we use Hikari and most teams use default connection pool size which may not be the optimal size. If we can right-size the connection pool size, it may reduce the memory and CPU usages. After that we can have a more accurate assessment of your RDS instances.

But for the connection-tuning part, we can do that only after we have enough data (after you enable the monitoring for at least a few days). The guide for connection-tuning will come soon.

Thank you!