Skip to main content
Latitude.sh provides robust monitoring capabilities for your databases, allowing you to track key performance metrics and understand resource utilization. This helps in diagnosing issues, optimizing performance, and ensuring the stability of your database instances.

​
Overview

The monitoring features are accessible directly from your database’s overview page within the Latitude.sh dashboard. You will find a dedicated “Monitoring” section that provides a quick glance at essential metrics. Key metrics displayed in the Monitoring section on the database overview page include:
  • CPU Usage: Shows the percentage of CPU resources being consumed by your database instance.
  • Memory Usage: Displays the percentage of memory currently in use by the database.
  • Transactions Per Second (TPS): Indicates the number of transactions your database is processing each second.

​
Monitoring Overview Page

For more in detail insights of your database’s performance over time, you can also see the dedicated monitoring overview page. To access this page:
  1. Go to the Databases section in the sidebar menu.
  2. Select the database you wish to monitor.
  3. Click on the “Monitoring” tab on the database overview page.
The monitoring overview page presents detailed charts for various metrics, including:
  • CPU Usage: A time-series chart showing CPU utilization trends.
  • Memory Usage: A time-series chart illustrating memory consumption patterns.
  • Transactions Per Second (TPS): A chart displaying the transaction rate over time.
  • Database Size: Shows the growth of your database size.
These charts allow you to observe historical performance, identify patterns, and make informed decisions about scaling or optimizing your database.

​
Storage Alerts

Latitude.sh automatically monitors your database storage usage and sends email alerts when capacity thresholds are reached. This proactive notification system helps prevent service interruptions caused by disk exhaustion.

​
How it works

  • Threshold: Alerts are triggered when storage usage reaches 85% capacity.
  • Recipients: All team members with administrator or owner roles receive email notifications.
  • Frequency: To avoid alert fatigue, there’s a cooldown period between notifications.

​
Why storage matters

PostgreSQL reserves approximately 5% of disk space for Write-Ahead Log (WAL) operations—a critical mechanism for data integrity and crash recovery. When your database reaches 95% total disk usage, WAL operations may fail, causing:
  • Connection disruptions
  • Transaction failures
  • Potential data loss
When you receive a storage alert:
  1. Upgrade your database plan - Scale to a larger plan with more storage capacity from your database settings.
  2. Remove unused data - Delete obsolete records, truncate logs, or archive historical data.
  3. Optimize storage - Run VACUUM FULL to reclaim space from deleted rows, or review large tables for optimization opportunities.
Storage alerts are sent automatically. No configuration is required—monitoring begins as soon as your database is deployed.