⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.23
Server IP:
178.33.27.10
Server:
Linux cpanel.dev-unit.com 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 x86_64
Server Software:
Apache/2.4.57 (Unix) OpenSSL/1.0.2k-fips
PHP Version:
8.2.11
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
usr
/
local
/
src
/
netdata
/
health
/
guides
/
postgres
/
View File Name :
postgres_total_connection_utilization.md
### Understand the alert This alert monitors the total `connection utilization` of a PostgreSQL database. If you receive this alert, it means that your `PostgreSQL` database is experiencing a high demand for connections. This can lead to performance degradation and, in extreme cases, could potentially prevent new connections from being established. ### What does connection utilization mean? `Connection utilization` refers to the percentage of `database connections` currently in use compared to the maximum number of connections allowed by the PostgreSQL server. A high connection utilization implies that the server is handling a large number of concurrent connections, and its resources may be strained, leading to decreased performance. ### Troubleshoot the alert 1. Check the current connections to the PostgreSQL database: You can use the following SQL query to check the number of active connections for each database: ``` SELECT datname, count(*) FROM pg_stat_activity GROUP BY datname; ``` or use the following command to check the total connections to all databases: ``` SELECT count(*) FROM pg_stat_activity; ``` 2. Identify the source of increased connections: To find out which user or application is responsible for the high connection count, you can use the following SQL query: ``` SELECT usename, application_name, count(*) FROM pg_stat_activity GROUP BY usename, application_name; ``` This query shows the number of connections per user and application, which can help you identify the source of the increased connection demand. 3. Optimize connection pooling: If you are using an application server, such as `pgBouncer`, that supports connection pooling, consider adjusting the connection pool settings to better manage the available connections. This can help mitigate high connection utilization. 4. Increase the maximum connections limit: If your server has the necessary resources, you may consider increasing the maximum number of connections allowed by the PostgreSQL server. To do this, modify the `max_connections` configuration parameter in the `postgresql.conf` file and then restart the PostgreSQL service. ### Useful resources 1. [PostgreSQL: max_connections](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-MAX-CONNECTIONS)