What Is Monitored
How It Works
Deploy
KPIs
Overview
GermainUX watches each PostgreSQL server your applications depend on and tells you when it’s in trouble. You see open connections climb towardmax_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
Locks and Bloat
Workload Shape
Scans and I/O
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 of1000 because an application leaks connections. The gap that follows is the time when the server refused new clients, the monitor included.

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 - GermainUX
SLAs and Alerts
Three KPIs come with a default SLA, evaluated per database data source: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
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,
5432by default, andpg_hba.confallows connections from the Engine host. - A PostgreSQL login with
CONNECTon 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 = oninpostgresql.conf. Without it, both stay at0.
Deploy
Add the JDBC driver to the Engine
lib folder of the GermainUX Engine installation, the folder for third-party jars such as JDBC drivers. Then restart the Engine.Add the database credentials
Add PostgreSQL as a data source

Database Data Source for PostgreSQL - GermainUX
Apply the PostgreSQL profile to the host

Apply the PostgreSQL Database Server Profile - GermainUX
Validate
Check availability
Check the metrics
SELECT count(*) FROM <table>;, and check that Database Return Rate or Database Sequential Scans rises.Troubleshooting
Applying the profile fails with "Unable to identify engine for server"
Applying the profile fails with "Unable to identify engine for server"
Database Availability shows the database as down
Database Availability shows the database as down
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.Database Read Time and Database Write Time stay at 0
Database Read Time and Database Write Time stay at 0
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.
KPIs
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.
Related Documentation
Query Monitoring
GermainUX Engine
Analytics
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
Can't Find What You Need?
The content of this document is proprietary to GERMAIN SOFTWARE.

