Skip to main content

​
Overview

The Nearbase console provides live monitoring data for every running instance across four areas: Performance, Usage, Error Logs, and Slow Query Logs.

​
Performance Tab

The Performance tab shows real-time and historical charts for the most important database metrics.
MetricDescription
CPU UsagePercentage of allocated vCPUs in use. Sustained high CPU suggests the instance class needs to be scaled up.
Memory UsagePercentage of allocated RAM in use. High memory pressure can cause query slowdowns and swapping.
Disk IOPSRead and write I/O operations per second. Useful for identifying I/O-bound workloads.
Active ConnectionsNumber of client connections currently open. Compare against your instance’s connection limit.
Slow QueriesCount of queries that exceeded the slow query threshold in the selected time window.
Long TransactionsCount of transactions open for an unusually long time. Long transactions can block vacuuming and cause lock contention.
If CPU or connections are consistently near their limits, consider scaling up your instance class or adding connection pooling in your application.

​
Usage Tab

The Usage tab shows aggregate resource utilization for the instance.
MetricDescription
Disk UsageTotal storage consumed vs. your provisioned storage size.
MemoryActual memory consumed by the database process.
Storage can only be scaled up, not down. Monitor disk usage and scale storage before you run out — the platform will alert you when usage is high.

​
Error Logs

The Error Logs tab streams PostgreSQL error log entries from your instance. Filtering:
  • Use the date range picker to view logs from a specific time window.
  • Results are paginated; use the navigation controls to scroll through older entries.
Common log entries to watch for:
Message PatternWhat It Means
FATAL: password authentication failedA client attempted to connect with wrong credentials.
ERROR: out of shared_buffersMemory pressure; consider scaling up or tuning shared_buffers.
FATAL: remaining connection slots are reservedConnection limit reached; reduce pool size or scale up.
ERROR: deadlock detectedTwo transactions were waiting on each other; one was rolled back.

​
Slow Query Logs

The Slow Query Logs tab lists queries that exceeded the slow query threshold, along with their execution time and query text. Filtering:
  • Use the date range picker to scope to a specific time window.
  • Results are paginated.
Using slow query logs:
  1. Sort by execution time to find the worst offenders.
  2. Run EXPLAIN ANALYZE on slow queries in psql to see the query plan.
  3. Add indexes on columns used in WHERE, JOIN, and ORDER BY clauses.
  4. Consider rewriting queries that perform sequential scans on large tables.
Slow query logging is enabled by default. The threshold is set in your instance’s PostgreSQL parameters — see Parameters.