VPS Watch Lite
Keep an eye on your personal Linux VPS without installing a monitoring stack. See CPU, RAM, root disk and inode usage with absolute capacities and compact history charts. Read system counters over SSH or import an existing collector history without running duplicate measurements; the optional collector caps VPS history at 32 MiB. Requires SSH key access to Linux; optional background collection requires a separate Python 3 and Docker systemd setup, with no paid service or external API.
Overview
View sourceWhat you get
Keep an eye on a personal Linux VPS from a BB sidebar panel. Resource cards show CPU, memory, root filesystem space and inode usage, with percentages and absolute capacities. See uptime, load averages and compact history charts for the last 1, 6 or 24 hours.
How it works
Choose direct SSH sampling or read-only import from an existing VPS history collector. The plugin makes one short SSH request per interval, starting at five minutes. It reads Linux system counters and root filesystem statistics. Direct mode installs nothing remotely and does not scan directories, logs or processes. History mode imports prepared summary records without running the collector or Docker again. Up to 288 successful measurements stay in BB storage.
CPU usage is averaged between measurements; the first measurement has no CPU value. The vCPU figure is an equivalent load across logical CPUs. Memory and disk capacities use binary units. Older measurements without capacities remain visible with unknown absolute values.
Setup and requirements
Open BB Settings, select VPS Watch Lite, enter an existing SSH alias and enable collection. The SSH client and configuration belong to the computer running the BB server. Key authentication and an already trusted host key are required. The target must run Linux with MemAvailable in /proc/meminfo and provide awk, cat and df.
Operating limits
Direct collection stops when BB is not running. An optional systemd collector continues independently and writes at most eight daily files of 4 MiB each (32 MiB total) on the VPS. It runs every five minutes and includes Docker statistics and a process-memory snapshot; Python 3, Docker and root installation are required for that optional collector. Connection failures leave the previous successful measurement visible with its timestamp. Gaps in charts are not joined. Manual checks respect the configured interval. This version provides dashboard warnings, with no push alerts, remote cleanup or service restarts. No external API, AI service or paid account is required.
More from Artur Karapetyan
More in Environments & Cloud 13
Create and manage where threads run, locally or in the cloud.

