Raspberry Pi monitoring, without weighing the Pi down

The agent package for ARM64 runs on a Raspberry Pi with Ubuntu 22.04 or newer. It installs the agent, the read-only helper and the moxivue command line, without a window, so it suits a Pi with no screen.

sudo apt install moxivue-agent
sudo moxivue service enable
sudo moxivue machine join <rendezvous>

The rendezvous comes from an owner's or admin's console (moxivue machine add). The Pi shows an 8-digit number: type it on that console, which then shows three words to type on the Pi.

With the MoxiVue package source added, apt picks the ARM64 package by itself; the ARM64 file is also on the download list. The agent then starts at boot with nobody signed in, as the system user moxivue, never as root, so the moxivue commands on the Pi run with sudo. The guide has every step.

• Load per core, clock speed and throttling events, with charts of temperature and clock over the last 5 to 60 minutes.
• Every temperature sensor the system exposes, and fan speeds.
• A temperature alert (default 90 °C), and thermal events from the kernel log on the fault list.
• Pressure: how much of the time apps were stalled waiting for memory, disk or processor.

A Pi that slows down when it gets warm is a common puzzle. Seeing the temperature, the clock and the throttling events side by side, and going back to the moment it happened in the history, tells you whether heat is the reason.

Every reading is kept for 30 days by default, with per-app totals in 30-minute blocks, so "it was slow last night" becomes a question you can answer: open the block and see the app. Export readings or per-app use as CSV for any range.

Alerts for processor, memory, disk space, temperature and pressure, and for activity far from the Pi's normal for that hour of the week, go to ntfy, Telegram, email, SMS or WhatsApp. The fault list, checked every 30 seconds, also catches full disks, failed services, file systems gone read-only and network problems; moxivue faults lists them on the Pi.

A Pi often sits on a network you want to keep an eye on. From there, MoxiVue maps the devices nearby by maker and type, hears what switches and access points announce (LLDP and CDP), and shows the path to the internet hop by hop, with gateway and internet latency, jitter and packet loss. On a Pi with Wi-Fi it shows the link, roams between access points and nearby networks; with an LTE or 5G modem, the operator, technology and signal through ModemManager.

If your account switches it on for the Pi, and a second console confirms, it can also be the way in to devices on its own network: open a router or NAS page, or SSH to a switch, through the Pi, sealed end to end, and wake a sleeping device. It only leads into networks the Pi is directly connected to; the security page says how this is locked down.

The Pi connects out to the MoxiVue Dispatcher, so there is nothing to open on your router. From your console you see its readings and, as an operator or above, open a terminal: off until your account switches it on for the Pi, only for the consoles it lists, never as root, and recorded. The Pi seals its readings, status and audit records with keys only the consoles of its site or group hold, and the Dispatcher stores them sealed.

MoxiVue is native code written in Rust, with no interpreter or runtime to install. On our Raspberry Pi 4 (4 cores, Ubuntu 24.04), averaged over 45 minutes with the default settings:

• Agent: 30 MB of memory. Helper: 5 MB.
• Processor, agent and helper together: 6.4% of one core, which is 1.6% of the machine.
• Traffic with the Dispatcher: about 1.3 MB a day.

Your figures will differ with the number of processes, interfaces and devices on the network. Check them at any time with ps -o rss,cputime,etime,comm -C moxivue-agent,moxivue-helper; the full measurements say how they were taken.