Skip to content
Features

Live Monitoring

Local Panel documentation · Features

Live server monitoring in Local Panel shows you the CPU, memory, disk and services of every server in your list, updated in real time over SSH. Nothing is installed on the server: the desktop app reads standard system information and streams it straight to your screen, so what you see is the server as it is right now, not a cached snapshot from an hour ago.

What live monitoring shows

Once you are connected to a server, the monitor view reports four things:

  • CPU — overall processor usage, so you can see how busy the server is.
  • Memory — how much RAM is in use, including swap activity where available.
  • Disk — how much of the filesystem is filled.
  • Services — which services are running, and which have stopped.

Because the connection is direct from your desktop to your server, the numbers arrive without an agent or a middleman. Your credentials stay on your device, encrypted by your operating system's keychain.

Before you start

You need at least one server in your list. If you have not added one yet, follow the Quick Start guide — it takes about five minutes. Then connect to the server and open its monitor view; the figures will begin updating straight away.

Reading the numbers

Server monitoring is most useful when you know what normal looks like. On a healthy small VPS — say a single-core box running a website and a database — idle CPU typically sits well below twenty per cent between requests, memory use stays fairly steady, and disk usage grows slowly, in small steps. Glance at your own servers over a few days and you will learn each one's baseline.

Sustained high CPU

CPU that jumps during a deploy or a backup is normal. CPU pinned near the ceiling for a long stretch usually means a process is stuck or the server is working harder than it can manage. Check which service is responsible before you reach for a bigger plan.

Memory pressure and swap

When RAM runs short, the server starts swapping to disk, and everything slows down. If memory use climbs steadily or swap stays active, a process may be leaking, or the workload has simply outgrown the machine.

A filling disk

Disk space rarely runs out suddenly. It fills with logs, old releases and databases growing a little every day. If the trend is upwards week after week, clear old files or add storage before it becomes an emergency.

A stopped service

If a service you expect to be running shows as stopped, your website, database or mail handling may already be down. Restart it, then look for the reason it stopped in the first place.

Watching several servers at once

If you look after more than one server, you do not need to open each in turn. The servers screen keeps the key status of your whole list in one view, so a quick glance is enough to spot the machine that deserves attention. Keep the panel open while you work and problems surface on their own, instead of being found by a visitor.

Pairing with Server Diff and scheduled commands

Monitoring tells you when a server drifts; Server Diff shows you where. Use the Server Diff screen to compare two servers side by side and see differences in packages and configuration. For recurring tidy-up — log rotation, cache clearing, routine checks — the Commands screen lets you schedule commands so they run on their own. Together, these three habits turn server maintenance from a fire drill into a quiet routine.

Still stuck? Email contact@nesdzo.co.uk — we're happy to help.