The problem
The load average climbs, every website on the server gets slow, and top over SSH shows a wall of php-fpm and httpd processes that all look the same. On a shared server with dozens of hosting accounts, the real question is never “is the CPU busy?” — it is which account, site or script is making it busy, and whether that is normal work or a runaway process.
Doing this by hand means juggling top, ps, per-pool PHP-FPM status pages and Apache logs — while the server is on fire.
The solution
VpsMonitor.Pro polls CPU, memory, IO-wait and network every few seconds over SSH and draws live charts with history, so you see the spike the moment it starts — from the Windows tray, no terminal needed.
One click on Details next to the CPU chart takes a full “who is loading the server?” snapshot: top processes, top users, PHP-FPM pools, running MySQL queries, busiest domains and long-running maintenance jobs (like certbot or backups) — each normalised so 100% means the whole server, not one core.
The Accounts view goes further: per-account CPU and memory, charted hourly, daily and monthly from the panel’s own statistics, so you can prove which customer’s site caused last night’s spike. If you want a second opinion, the built-in Analyze with AI button sends the snapshot to Claude or ChatGPT for a plain-language verdict and prioritised next steps.
Frequently asked questions
Does VpsMonitor.Pro install anything on my server?
No. It is agentless — it connects over SSH like you would, runs read-only commands, and keeps all history in a local SQLite database on your Windows PC.
How do I know if 100% CPU is one core or the whole server?
The app normalises every value by the server’s core count, so 100% always means the entire server is busy. A single hot core shows as 12.5% on an 8-core VPS.
Can it alert me before users complain?
Yes — set a CPU threshold and you get an email (and optionally a Telegram message) the moment the one-minute average crosses it.
Get a license · Download free — 7-day trial