Postgresql too many locks acquired critical
>>>
((sum (
pg_locks_count
)) / (
pg_settings_max_locks_per_transaction
*
pg_settings_max_connections
)) > 0.20
The rule computes the ratio of the total number of locks currently held (pg_locks_count) to the maximum possible locks (pg_settings_max_locks_per_transaction * pg_settings_max_connections). If this ratio exceeds 0.20 (i.e., more than 20 % of the available locks are in use), the alert triggers, suggesting that the max_locks_per_transaction setting may need to be increased.
Exporters Used
Related Alerts
PostgreSQLCacheHitRatio
PostgreSQLDown
PostgreSQLHighConnections
PostgreSQLMaxConnectionsReached
PostgreSQLQPS
PostgreSQLSlowQueries
Postgresql SSL compression active
Postgresql bloat index high (> 80%)
Postgresql bloat table high (> 80%)
Postgresql commit rate low
Postgresql configuration changed
Postgresql dead locks
Postgresql down
Postgresql exporter error
Postgresql high rate deadlock
Postgresql high rate statement timeout
Postgresql high rollback rate
Postgresql invalid index
Postgresql low XID consumption
Postgresql not enough connections
Postgresql replication lag
Postgresql restarted
Postgresql table not auto analyzed
Postgresql table not auto vacuumed
Postgresql too many connections
Postgresql too many dead tuples
Postgresql unused replication slot