> ## Documentation Index
> Fetch the complete documentation index at: https://www.latitude.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Database Monitoring

Latitude.sh provides monitoring capabilities for your databases, allowing you to track performance metrics and understand resource utilization. This helps diagnose issues, optimize performance, and ensure database stability.

## Accessing Monitoring

To access monitoring for any database:

1. Go to the **Databases** section in the sidebar menu.
2. Select the database you want to monitor.
3. View the **Monitoring** section on the overview page for a quick summary.
4. Click the **Monitoring** tab for detailed charts.

### Overview Page Metrics

The database overview page displays real-time sparklines for:

* **CPU Usage**: CPU utilization percentage
* **Memory Usage**: Memory consumption percentage
* **Transactions Per Second (TPS)**: Transaction throughput rate

### Monitoring Page

The monitoring page provides detailed time-series charts:

* **CPU Usage**: CPU utilization over time
* **Memory Usage**: Memory consumption over time
* **Transactions Per Second (TPS)**: Transaction rate over time
* **Database Size**: Storage growth over time

Use the period selector to adjust the time range for all charts, from 30 minutes to 7 days.

## 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

### Recommended actions

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.

<Note>
  Storage alerts are sent automatically. No configuration is required—monitoring
  begins as soon as your database is deployed.
</Note>