Resource Usage

Server Resource Usage compares current and historical consumption across hosted accounts so an administrator can find sustained pressure rather than guess from one busy minute.

Where to find it: Open the Server menu and choose Resource Usage. Conditional items appear only when their service is installed and available.

Available to: Root only.

What this page does

Use Resource Usage for provider operations in the server scope. Read the current state first because actions here may affect several accounts or shared services.

Before you start

Resource Usage is an evidence page. Refresh it in the correct scope and correlate the result with the owning service or logs before using a disruptive action.

Why use it — and when not to

Use Resource Usage when you need current evidence or a bounded status view. Do not use one snapshot as the only basis for a destructive action; correlate it with time, scope, logs, and the affected service.

How to use it

1. Choose the exact account, domain, service, process, or time range.
2. Refresh the data and read the status in context.
3. Correlate it with logs or a second status source before taking action.
4. If an action is needed, use the smallest supported action and refresh again.

Result and next check

Opening or refreshing Resource Usage does not change configuration. If the page offers an action such as kill, clear, retry, or restart, that action has its own impact and must be confirmed separately.