It monitors Postgres DB agent metrics like activity long transactions.
The database you want to monitor should connect from the Gateway. Gateway Management profile should be added to the device. Database type credentials should be added against the device in the portal.
|Frequency||Warning Threshold||If the metric value satisfies the condition defined along with Warning Threshold value, then a notification is sent to the user.|
|Critical Threshold||If the metric value satisfies the condition defined along with Critical Threshold value, then a notification is sent to the user.|
|Alert||The alert value can be set to either Yes or No. If it is Yes, then an alert message is sent to the user.|
|Description||Long-running transactions are bad because they prevent Postgres from vacuuming old data. This causes database bloat and, in extreme circumstances, shutdown due to transaction ID (xid) wraparound. Transactions should be kept as short as possible, ideally less than a minute.|
|Monitor Name||G2 PostgreSQL Database CPU Utilization Monitor|
|Metric||Input Value||Range of Values|
|Warning Repeat Count|
|Critical Repeat Count|