Enter the operator access password configured in .env to decrypt cluster telemetry.
🐘
DB_OPS PostgreSQL 18.6
Production Cluster Telemetry · chat360chatbot
● 2m Interval
CLUSTER TOPOLOGY:PRIMARY[168.144.85.202:5432]══ streaming WAL ══►REPLICA[64.227.187.244:5432]WAL: In Sync (0 B)Initializing telemetry…
👑
Production Master
168.144.85.202:5432 · chat360chatbot
Checking…
— / —
Active / Total Conns
—
Idle / In TX
—
Running Queries
—
Slow Queries (>10s)
—
Database Size
—%
Cache Hit Ratio
Pool Capacity Utilization0%
⚡ Zero-Load DB Optimization Telemetrypg_stat in-memory
—%
Index Hit Ratio
—%
Index Scan Ratio
—%
Table Bloat (Dead)
—
Temp Disk Spills
0
Deadlocks
0
Autovacuum Active
📖
Production Read Replica
64.227.187.244:5432 · chat360chatbot
Checking…
— / —
Active / Total Conns
—
Idle / In TX
—
Running Queries
—
Slow Queries (>10s)
—
Database Size
—
Replication Lag
Pool Capacity Utilization0%
Replication Attribution:In Sync
Master: 0 B · Reader: 0 B
⚡ Zero-Load DB Optimization Telemetrypg_stat in-memory
—%
Index Hit Ratio
—%
Index Scan Ratio
—%
Table Bloat (Dead)
—
Temp Disk Spills
0
Deadlocks
0
Autovacuum Active
🔄 Replication Lag Attribution & Pipeline Breakdown
Live root-cause attribution: distinguishes whether lag is from Master Send Delay (Master didn't send WAL) or Reader DB Replay Delay (Reader DB received WAL but hasn't applied it yet).
In Sync
✅
Replication In Sync
Primary Master and Read Replica are fully in sync with 0 B replication lag. All WAL logs have been transmitted and applied.
Root Cause: None · Streaming and Replay in Sync
STAGE 1
👑 Primary Master (Send)
0 B
Master Send Lag
Master Status:All WAL Sent
Current WAL LSN:—
Write/Network Delay:0.00s
Master Side: WAL produced on Master but not yet received by Reader DB.
STAGE 2
⚡ Streaming WAL Transport
Streaming
Connection Mode
Standby Client:64.227.187.244
Sync State:async
Total End-to-End Lag:0 B
Active TCP replication link between Primary and Read Replica.
STAGE 3
📖 Reader DB (Replay & Apply)
0 B
Reader Apply Lag
Reader Status:Fully Applied
Received LSN:—
Replayed LSN:—
Replay Time Lag:0.00s
Reader DB Side: WAL received by Reader DB but not applied yet into tables.
Node
PID
User / App
State
Wait Event
Duration
Query Start
SQL Statement
Action
Loading active sessions…
Showing 0 of 0
From:To:
Node
PID
User
Duration
Threshold
Status
First Seen
Last Seen
SQL Statement
Action
Loading slow queries…
Showing 0 of 0
Connection Activity (Active vs Idle vs Total)
Cache Hit Ratio % & Active Locks
Database Size Telemetry (MB)
WAL Replication Lag (Bytes)
👑 Primary Node: Connected Standbys
pg_stat_replication active receivers
Loading replication details…
📖 Replica Node: WAL Replay Status
pg_stat_wal_receiver & LSN positions
Loading recovery details…
🛡️
Safe Storage Deletion Guarantee
This operation ONLY purges historical metric logs from the internal db_metrics storage database.
The primary production database and read replica (chat360chatbot) are strictly read-only and are NEVER touched, modified, or altered.
📦 Metrics Database Storage Usage
Tables in db_metrics
Table
Rows
Disk Size
Oldest Record
Newest Record
Loading table metrics…
Total Monitored Tables: 3Total Storage Used: —
🗑️ Purge Historical Metrics
Execute an asynchronous background deletion to free up space.