Server Metrics

Users of single-tenant database plans (currently: Whitetip, Thresher, Tiger, Hammerhead, and Goblin), have access to graphs of important database metrics for CPU, storage, and IO. They can be accessed through the dashboard on the ‘Server Status’ panel.

The metric data points are spaced 5-minutes apart and can be viewed for periods of:

  • The last hour
  • The last 3 hours
  • The last day
  • The last 3 days
  • The last week

Below is a brief description of the included metrics.

  • CPU Utilization - The percentage of the CPU in use. CPU usage in database applications is typically low. A consistently high value here may indicate slow queries and the need to index tables. If indexes are already optimized, the CPU on this plan may simply be underpowered for your application. A plan upgrade should be considered.
  • Read IOPS - The average number of Read-specific IO operations per second to disk. A high value here indicates there is not enough RAM available on this plan to store the application’s frequently requested data in memory.
  • Write IOPS - The average number of Write-specific IO operations per second to disk.
  • Free Storage - The free storage in GB for the server.
  • Read Latency - The average time taken per read-specific IO operation on disk.
  • Write Latency - The average time taken per write-specific IO operation on disk.
  • Disk Queue Depth - The average number of outstanding IOs (read/write requests) waiting to access the disk.
  • Network Transmit Throughput - The outgoing network traffic on the server in MB.
  • Network Receive Throughput - The incoming network traffic on the server in MB.

Using these metrics can be the first step in troubleshooting performance issues and traffic spikes. While a plan upgrade will usually solve issues with poor performance, a metric performing poorly may not necessarily indicate a need to upgrade plan. Instead, performance issues can often be fixed by better indexing or optimizing queries or making modification to database structure.