Skip to content

Metrics

Review storage, bandwidth, inode, and resource use.

1Overview

Metrics reports the account resources measured by the panel, including disk, bandwidth, inode, and package-related use where available.

Metrics in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Resource insights showing CPU activity, process memory, active processes, disk throughput, and resource history graphs.

Metrics in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

User-panel actions affect only resources owned by the signed-in hosting account. This is an advanced task; schedule it carefully and keep a rollback path.

3Step-by-step workflow

Open Metrics, compare current use with your package limits, identify the affected website, mailbox, backup, or file set, and clean up or request a package change before reaching the limit.

  1. Open Metrics and read Resource insights for the signed-in hosting account.
  2. Choose a time range that matches the period you want to investigate.
  3. Compare CPU activity, process memory, active processes, and disk throughput rather than looking at one value alone.
  4. Use Refresh when you need a new reading; automatic page updates occur every hour.
  5. Open Directory disk usage and choose Measure home folder or a supported directory measurement.
  6. Wait for measurement to finish and open the larger folders to identify what uses space.
  7. Review traffic statistics separately from disk size and package storage limits.
  8. Remove only confirmed unnecessary files or ask the provider for a package change, then measure again.

4Practical example

Example: a large backups folder can explain storage use without high CPU activity. A short CPU spike during a backup does not by itself mean your account is out of disk space.

5Time ranges, directory sizes, and resource readings

The time-range selector changes how much history is displayed. It does not change the one-hour automatic refresh interval. Use the last-update time and manual Refresh to distinguish an old sample from a current reading.

Directory usage helps locate space in websites, uploads, mail, caches, and backups. Parent folder sizes include their contents, so adding a parent and all child sizes counts the same data more than once. A large number of tiny files can also use the account file-count allowance.

6Verify the result

Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.

  1. Confirm the selected limit has sufficient headroom.
  2. Check that cleanup did not remove required site, mail, or backup data.

7Common problems and what to check

The graph does not update every few seconds: hourly automatic updates are expected; use Refresh for a manual check.

Directory sizes are missing: run a measurement and allow it to finish, especially on an account with many files.

Process memory differs from a package allowance: it is observed resident memory, while storage and package limits are separate measurements.

8Security, impact, and rollback

Do not delete backups, databases, or mail just to reduce usage without confirming retention needs. High inode usage is often caused by many small files, caches, or mail messages.

Related guides

Billing and SupportOpen the client area and create useful support requests.Hosting PasswordChange the password for your hosting account.See all guides in User hosting panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area