Description

It monitors Postgres DB agent metrics like activity long transactions.

Prerequisites

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.

Metric Parameters

Metric Parameters
ParameterDescription
Frequency
  • Frequency is the interval in which you want to probe and collect metric data from the target device/resource
  • Frequency is defined in minutes (min).
    • Warning ThresholdIf the metric value satisfies the condition defined along with Warning Threshold value, then a notification is sent to the user.
    Critical ThresholdIf the metric value satisfies the condition defined along with Critical Threshold value, then a notification is sent to the user.
    AlertThe alert value can be set to either Yes or No. If it is Yes, then an alert message is sent to the user.

    Metrics

    postgresql.activity.long_transactions

    Metric Details

    Metric Details
    Applicable forDevice
    DescriptionLong-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.
    CategoryApplication
    Collector TypeGateway
    Monitor NameG2 PostgreSQL Database CPU Utilization Monitor
    Unith

    Possible Inputs

    Possible Inputs
    MetricInput ValueRange of Values
    Frequency5Manual
    Filter
    Warning Operator
    Warning Threshold
    Warning Repeat Count
    Critical Operator
    Critical Threshold
    Critical Repeat Count
    AlertNoYes/No
    Graph (Yes/No)YesYes/No

    Sample Output

    No graph