What to check
A useful review order
1
Check health
Make sure the instance is healthy or running before investigating application errors.
2
Compare connections and latency
A rise in both can point to slow queries, connection leaks, or a traffic spike.
3
Review storage and transfer
Look for a growing dataset, a large migration, or unexpected data movement.
4
Review resource usage
If the workload is close to its limit, open Settings before changing application connection settings.
Monitoring versus application logs
Database monitoring shows the service and resource view. Your project Live Logs show the application’s connection errors, query errors, and retry behavior. Check both when an application can reach its route but database requests are failing.API access
Server-side automation can read database usage and metrics through the Database API. Keep API keys out of browser code and grant only the access required by the monitoring job.Monitoring checklist
- Confirm the database is running.
- Check whether connections are increasing without falling back.
- Compare latency with recent deployments and migrations.
- Check storage before it reaches the assigned limit.
- Review project Live Logs for the matching error window.
- Use Connection to confirm the application is using the current endpoint.