Skip to main content

Server Detail

The Server Detail page provides a comprehensive view of a single monitored PostgreSQL server — its current health, real-time metrics, top queries and database statistics. Everything is displayed on a single scrollable page.


Accessing Server Detail

From the Global Dashboard, click on any server row to open its detail page.

Server Detail


1. Server Header

The header displays the full identity and current state of the server at a glance.

FieldExampleDescription
Server Namepg-labServer display name as registered in the platform
StatusRUNEnvironment — RUN (production) or BUILD (non-production)
PostgreSQL VersionPostgreSQL 16.10Detected PostgreSQL version
Hostpg-labHostname of the monitored server
Port5432PostgreSQL listening port
Data Directory/var/lib/pgsql/16/dataPostgreSQL data directory path
Agent StatusRUNNINGCurrent agent status
Agent Versionv1.0.0Installed agent version

2. Quick Navigation

Three buttons at the top of the page provide direct access to the analysis tools for this server:

ButtonDestination
ASH ViewerReal-time activity monitoring for this server
AWR ViewerProactive workload reports for this server
TrendsLong-term evolution charts for this server

Clicking these buttons automatically selects the current server — no need to use the server selector dropdown on the analysis pages.


3. Real-Time Metric Cards

Three summary cards display the current state of the server, refreshed automatically:

CardDescription
Active SessionsNumber of sessions currently active on the PostgreSQL instance
CPU UsageCurrent CPU utilization of the server host
Memory UsageCurrent memory utilization of the server host

4. Active Sessions — Real-Time Chart

A live chart showing the number of active sessions over the last 5 minutes, refreshed every 3 seconds.

This gives an immediate visual of current database activity and helps detect sudden session spikes before they become incidents.

Active Sessions


5. Top Queries

A table of the Top 5 SQL queries currently observed on the instance, ranked by total execution time.

ColumnDescription
QueryNormalized SQL text (truncated)
CallsTotal number of executions
Total TimeCumulative execution time
Avg TimeAverage execution time per call

Query Detail

Click on any query row to expand its full detail panel:

SQL Query Full normalized SQL text of the statement.

Execution Statistics

MetricDescription
Total CallsTotal number of executions
Total TimeCumulative execution time
Average TimeAverage time per execution
Min TimeFastest execution observed
Max TimeSlowest execution observed
Std DeviationExecution time variability

I/O & Cache

MetricDescription
Cache Hit RatioPercentage of block reads served from buffer cache
Cached BlocksBlocks read from buffer cache
Blocks ReadBlocks read from disk
Total RowsTotal rows returned across all executions
Avg Rows/CallAverage rows returned per execution

Query Detail


6. Database Statistics

A table of the Top 5 databases on the instance with key throughput indicators.

ColumnDescription
DatabaseDatabase name
TPSTransactions per second
CONNumber of active connections
CacheBuffer cache hit ratio

Database Detail

Click on any database row to expand its full statistics panel:

Main Metrics

MetricDescription
TPSTransactions per second
Active ConnectionsCurrent number of active connections
Cache Hit RatioBuffer cache efficiency percentage
Modified TuplesRows modified (INSERT + UPDATE + DELETE)

Transactions

MetricDescription
CommitsTotal committed transactions
RollbacksTotal rolled-back transactions
Total TransactionsCommits + Rollbacks

I/O & Cache

MetricDescription
Cached Blocks (hit)Blocks served from buffer cache
Blocks Read (disk)Blocks read from disk
Read Time (ms)Time spent reading from disk
Write Time (ms)Time spent writing to disk

Tuple Activity

MetricDescription
Rows ReturnedTotal rows returned by queries
Rows FetchedTotal rows fetched by queries
Rows InsertedTotal rows inserted
Rows UpdatedTotal rows updated
Rows DeletedTotal rows deleted

Temporary Files

MetricDescription
Number of Temp FilesTemporary files created (indicates sort/hash spills)
Total SizeTotal size of temporary files

Database Detail

tip

A high number of temporary files indicates that queries are spilling to disk during sort or hash operations. Consider increasing work_mem in postgresql.conf or reviewing query plans for missing indexes.


Next Steps