Skip to main content
ComponentsEngine
Availability8.6.15 or later

What Is Monitored

Connections, rows, scans, I/O

How It Works

One monitor on the Engine

Deploy

Data source and profile

KPIs

15 database KPIs

Overview

GermainUX watches each PostgreSQL server your applications depend on and tells you when it’s in trouble. You see open connections climb toward max_connections, deadlocks and dead rows pile up behind a stuck transaction, and sequential scans take over after an index goes missing. The PostgreSQL Overview dashboard and default SLAs on availability, connections and deadlocks work as soon as the monitor runs. Your team finds the database cause of a slow application without logging in to psql on every server. This page covers PostgreSQL databases that you monitor. To use PostgreSQL as the GermainUX datastore, see PostgreSQL Database Setup.

Connection Pressure

The number of open backend connections, with an SLA that fires before the server refuses new clients.

Locks and Bloat

Deadlocks, dead rows and HOT updates show a long transaction or a vacuum that can’t keep up.

Workload Shape

Rows returned, fetched, inserted, updated and deleted per second, so a runaway query or a bulk load stands out.

Scans and I/O

Sequential against index scans, temporary files written, and the time spent reading and writing blocks.

Questions It Answers

  • Is the PostgreSQL server up, and since when was it unreachable?
  • Are we running out of connections, and on which server?
  • Did a long transaction cause deadlocks or a pile of dead rows?
  • Which server suddenly reads far more rows than usual?
  • Did sequential scans jump after a deployment or a dropped index?
  • Are queries spilling to temporary files or waiting on disk I/O?

What Is Monitored

Analytics, Alerts and Automation

Root Cause Analysis

Open a KPI in the Analysis screen to compare the selected period with the previous days, and see which servers and databases changed most. In the example below, connections on pg-prod-01 climb past the SLA threshold of 1000 because an application leaks connections. The gap that follows is the time when the server refused new clients, the monitor included.
Analysis screen for the Database Connections KPI, with connections on pg-prod-01 climbing past 1000 and then a gap while the server refuses new connections

Analysis of Database Connections - GermainUX

AI Analysis

Ask AI Explore questions such as “When did connections on pg-prod-01 last pass 900?” and get the answer without building a report. Outlier detection flags unusual spikes in row rates, scans or temporary files.

Dashboards and Reports

GermainUX ships the PostgreSQL Overview dashboard. In the left menu, go to Dashboards > All, and then open PostgreSQL Overview in the PostgreSQL folder. It shows database availability, then one trend chart for each of the other KPIs: connections, deadlocks, the five row rates, HOT updates, dead rows, temporary files, read and write time, and sequential and index scans.
PostgreSQL Overview dashboard with database availability and trend charts for connections, deadlocks, row rates, dead rows, temporary files, I/O time and scans, during a long transaction on pg-prod-01

PostgreSQL Overview Dashboard - GermainUX

Click a chart to open the KPI behind it in the Analysis screen, or build your own dashboards and reports on the same KPIs.

SLAs and Alerts

Three KPIs come with a default SLA, evaluated per database data source: Change the thresholds to match your servers, for example a connection threshold below your max_connections. Add SLAs to the other KPIs, and get an alert by email, SMS, Slack or Teams when one is breached.

Correlation with Other Technologies

Correlate PostgreSQL KPIs with the application servers and user sessions that use the database, so you can tell whether a slow page comes from the database or from somewhere else.

How It Works

pg_stat viewsPostgreSQL monitorKPIsSLAsAlerts
GermainUX monitors PostgreSQL from a GermainUX Engine over JDBC. You don’t install anything on the database server. Each poll runs two short queries against these statistics views, so the monitor adds very little load to the server.

Before You Start

  • A GermainUX Engine is deployed and configured for the PostgreSQL host in Settings > Data Sources. See GermainUX Engine.
  • The Engine can reach the PostgreSQL port, 5432 by default, and pg_hba.conf allows connections from the Engine host.
  • A PostgreSQL login with CONNECT on the database. The statistics views GermainUX reads are readable by every user by default.
  • The PostgreSQL JDBC driver jar (postgresql-<version>.jar) from jdbc.postgresql.org. GermainUX doesn’t ship it.
  • For Database Read Time and Database Write Time, track_io_timing = on in postgresql.conf. Without it, both stay at 0.

Deploy

1

Add the JDBC driver to the Engine

Copy the PostgreSQL JDBC driver jar into the lib folder of the GermainUX Engine installation, the folder for third-party jars such as JDBC drivers. Then restart the Engine.
2

Add the database credentials

In the left menu, go to Settings > Data Sources > Credentials, and add the user name and password of the PostgreSQL login.
3

Add PostgreSQL as a data source

In the left menu, go to Settings > Data Sources. On the Databases tab, click Add New Configuration, and fill in the fields:Save the data source.
Database data source form with PostgreSQL selected as the Vendor, host pg-prod-01, port 5432 and the database name inventory

Database Data Source for PostgreSQL - GermainUX

4

Apply the PostgreSQL profile to the host

On the Hosts tab, select the PostgreSQL host, and then click the Apply Profile icon. Select PostgreSQL Database Server, click Apply, and fill in the fields:Finish the dialog. GermainUX deploys the monitor to the Engine of that host and starts polling.
Apply Profile dialog with the PostgreSQL Database Server profile and its Application, Credentials and Database fields

Apply the PostgreSQL Database Server Profile - GermainUX

Repeat the last two steps for each PostgreSQL server, for example a primary and its standby.

Validate

1

Check availability

In the left menu, go to Dashboards > All, and open PostgreSQL Overview in the PostgreSQL folder. After the first poll, Database Availability shows the database as up.
2

Check the metrics

After the second poll, the trend charts show data. Run a query that reads a table in the monitored database, such as SELECT count(*) FROM <table>;, and check that Database Return Rate or Database Sequential Scans rises.

Troubleshooting

No GermainUX Engine is configured for the host you selected. Deploy an Engine for that host, or apply the profile to a host that has one, and try again.
GermainUX stores the connection error with each failed check, in the details of the Database Availability KPI. The usual causes are a missing JDBC driver in the Engine’s lib folder, a pg_hba.conf entry that doesn’t allow the Engine host, a firewall on the PostgreSQL port, or a wrong password in the credentials.
PostgreSQL records block I/O time only when track_io_timing is on. Set track_io_timing = on in postgresql.conf, and reload the configuration.

Security and Privacy

PostgreSQL monitoring collects statistics, not table data or query text. It includes:
  • Infrastructure data: the host name of the database server and the name of the data source
  • Connection errors: when the database is down, the error message, which can contain the host, its address and the monitoring user name. Treat it as possibly containing personal or customer data.
To mask, anonymize or exclude this data, see Data Privacy.

KPIs

All 15 KPIs use the GenericMetric data model, and other database integrations share some of them. See SLAs and Alerts for the default SLAs, and KPIs for working with KPIs.

Query Monitoring

KPIs from your own SQL

GermainUX Engine

Where the monitor runs

Analytics

More Analytics Features

Get Help

The GermainUX team can help you monitor PostgreSQL clusters with many databases, or add KPIs from your own statistics queries.

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't Find What You Need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.