The PostgreSQL database uses an amount of disk cache to process each transaction. The more transaction requests received by the database the more of the database's allotted cache is used.
You can use the PostgreSQL KM's Database cache usage attribute to set a threshold warning and alarm that will alert you when the threshold value is crossed. If the threshold is crossed, the KM generates an event that can be viewed by the Database cache usage graph.
Database cache usage graph
You can then determine if the disk cache that the PostgreSQL database can use is sufficient for the amount of received transactions, or whether it needs to be increased.
As connections are made to the PosgreSQL database, you will want to monitor how many connections are made to the database and how many database elements are locked at one time, or are waiting to get a lock.
You can use the PostgreSQL KM's Number of connections, Number of elements waiting to get a Lock, or Number of locked elements attributes to set a threshold warning and alarm that will alert you when the threshold value for any of these attributes is crossed. For instance, if the number of connections surpasses the attribute's threshold, the KM generates an event that can be viewed by the Number of connections graph.
Number of connections graph
With this graph, you can see the number of connections that the PostgreSQL is handling and decide if the amount needs to be adjusted.
You can read about additional attributes in the Using topics. These attributes provide valuable data that lets you monitor the activity and health of the PostgreSQL database.