Resource Usage
Resource Usage shows what every account is actually consuming, live, against its plan limits: CPU, memory, disk, inodes, disk I/O and process count, per user. The numbers come straight from the kernel's own accounting (cgroups v2 and filesystem quotas), so they reflect real enforcement, not estimates.
Monitoring → Resource Usagehttps://YOUR-SERVER-IP:8443/resource-usage| User | CPU | RAM | Disk | PID | Status |
|---|---|---|---|---|---|
| john | 12% / 100% | 340 / 512 MB | 4.2 / 5 GB | 18 / 50 | Normal |
What it measures
The page is per user, not per domain, because Panelica isolates resources at the user level: all of an account's domains share its cgroup slice. Four cards count total users, quota-exceeded, high-usage (any resource at 75%+) and normal accounts. The table then shows, for each user, their plan, and live: CPU (percent of their limit), RAM (used/limit), disk (used/limit), inodes (used/quota, when kernel quotas are active), IO read/write rates, process count (used/limit), the plan's quota mode, and a status badge. Bars turn amber at 75% and red at 90% of the limit, and the busiest accounts sort to the top automatically.
cpu.stat, memory.current, io.stat, pids.current) and its filesystem quota counters via a kernel syscall (no slow du where quotas are on), computing rates from deltas between reads. Results are cached for a few seconds and served stale-while-fresh, so the page stays responsive even with hundreds of accounts. Refresh interval is adjustable (1 to 20 seconds) with a pause toggle.What "quota exceeded" means here
The status badge is a live indicator, and it is worth understanding exactly what enforces the limit, because it is not this page.
Access
Behind the resource_usage_dashboard license feature (Pro and up). Visibility follows the roles and permissions chain: a user sees only themselves, a reseller their customers, an admin their chain, ROOT everyone. The limits shown are the account's plan limits; how those limits are set lives in Hosting Plans.