As the hosting operator, enable PD AWS MySQL Usage Graphs for your customers and use the readings alongside your team’s workload checks. These provider measurements cover a selected period; they do not establish application health by themselves.

Customer steps: review the service and window

1. Confirm the service’s backing and current database state.
2. Open Usage Graphs and inspect the chart time range.
3. Review CPU utilisation, connections, freeable memory and free storage.
4. Compare the sample times with the application event you are investigating.
5. Check recent Activity for a reboot, snapshot or plan change that may explain the pattern.

Check the offering’s usage-graph control and the account’s permission to read the relevant provider metrics. Missing data is not the same as a zero reading.

Interpret the charts together

High connections or CPU can explain pressure that a storage change will not fix. Falling free storage needs separate review from available memory. Averages can hide short peaks, so use the provider or application’s more detailed investigation where needed.

Lightsail reports free memory as well as the other displayed database metrics; an empty graph should not automatically be dismissed as an unsupported Lightsail feature. AWS describes its database health metrics.

Diagnose an empty graph

As the hosting operator, check the database state, metric window, account permission and displayed read error against the same resource in AWS. A successful RDS connection test does not establish every metric permission or Lightsail API call works. If the graphs load correctly but the application is slow, continue workload diagnosis with your database administrator.

Use RDS plan changes or storage growth after establishing the actual capacity need and a recovery plan.

See the PD AWS MySQL WHMCS guide for related tasks, or explore PD AWS MySQL.