Skip to main content

Overview

The Overview tab provides a high-level view of your PostgreSQL cluster's health and performance. It's designed to give you immediate visibility into the most critical metrics at a glance.

Overview


Sections​

The Overview tab is organized into three main sections:

  1. Topology — Visual representation of connections and replication
  2. Stats — Key health metrics as stat panels
  3. Detailed View — Time-series charts for trend analysis

Topology Section​

The Topology section provides visual graphs showing how your applications and replicas are connected.

Application Connections​

A node graph visualization showing which applications are connected to your PostgreSQL cluster.

Application Connections

What it shows:

  • Connected applications by name
  • Connection distribution across the cluster
  • Active connection paths

How to use it:

  • Identify which applications are consuming connections
  • Spot unexpected connection sources
  • Verify application connectivity after deployments

Replica Topology​

A node graph showing the replication structure of your cluster.

Replica Topology

What it shows:

  • Primary and standby nodes
  • Replication relationships
  • Synchronous vs asynchronous replicas

How to use it:

  • Verify replication topology is as expected
  • Identify replication chain structure
  • Spot disconnected standbys quickly

Stats Section​

Six stat panels displaying the most critical health indicators.

Stats Section

Health Check​

What it shows: Whether PostgreSQL is up and responding.

ValueMeaning
UPPostgreSQL is responding to connections
DOWNPostgreSQL is not reachable

When to investigate: Immediately if showing DOWN.

Average Response Time​

What it shows: The average query response time across the cluster.

Healthy range: Depends on your workload, but typically < 100ms for OLTP.

When to investigate:

  • Sudden increases in response time
  • Response times exceeding your SLA thresholds

Cluster Database Size​

What it shows: The total size of all databases in the cluster.

How to use it:

  • Monitor storage growth
  • Plan capacity upgrades
  • Detect unexpected growth

Current Connections​

What it shows: The number of active connections to PostgreSQL.

When to investigate:

  • Approaching max_connections limit
  • Sudden spikes in connection count
  • Unusually low connections (may indicate application issues)

Transaction Error Rate​

What it shows: The percentage of transactions that resulted in errors (rollbacks).

Healthy range: Typically < 1% for most workloads.

When to investigate:

  • Error rate exceeding normal baseline
  • Sudden spikes in errors
  • Sustained elevated error rates

Cache Hit Ratio​

What it shows: The percentage of data reads served from the buffer cache vs disk.

Healthy range: > 99% for most OLTP workloads.

When to investigate:

  • Cache hit ratio below 95%
  • Declining trend over time
  • After significant schema or query changes

Detailed View Section​

The Detailed View section provides time-series panels for trend analysis. This section is collapsed by default — click to expand.

Detailed View

Database Growth Rate​

What it shows: The rate at which your database size is growing over time.

How to use it:

  • Forecast storage needs
  • Identify periods of high data ingestion
  • Detect data growth anomalies

Deadlock Count​

What it shows: The number of deadlocks occurring over time.

Healthy range: Zero or near-zero for most workloads.

When to investigate:

  • Any deadlocks occurring
  • Increasing trend in deadlock frequency
  • Deadlocks correlating with specific time periods

Connection Failure Rate​

What it shows: The rate of failed connection attempts.

Healthy range: Zero for healthy systems.

When to investigate:

  • Any connection failures
  • Correlation with application errors
  • Spikes during high-traffic periods

Use Cases​

Morning Health Check​

Start your day by reviewing the Overview dashboard:

  1. Verify Health Check shows UP
  2. Check Cache Hit Ratio is in healthy range (> 99%)
  3. Confirm Transaction Error Rate is normal
  4. Review Current Connections for expected levels

Post-Deployment Monitoring​

After deploying application changes:

  1. Watch Average Response Time for degradation
  2. Monitor Transaction Error Rate for increased errors
  3. Check Application Connections topology for expected patterns
  4. Review Connection Count for proper scaling

Capacity Planning​

Use the Overview dashboard for capacity planning:

  1. Track Cluster Database Size growth
  2. Monitor Database Growth Rate trends
  3. Watch Current Connections vs max_connections
  4. Review patterns over time in the Detailed View

The Overview section uses these metrics from the Metrics Reference:

PanelPrimary Metrics
Health Checkpg_up
Response Timepg_statement_stats
Database Sizepg_database_size_bytes
Connectionspg_connections, pg_database_stats.num_backends
Error Ratepg_database_stats.xact_rollback, pg_database_stats.xact_commit
Cache Hit Ratiopg_database_stats.blks_hit, pg_database_stats.blks_read
Growth Ratepg_database_size_bytes
Deadlockspg_database_stats.deadlocks

Was this page helpful?