Once you host DNS, DHCP, file sharing, a dozen containers, and several VMs all on a single ZimaCube, an uncomfortable truth gradually becomes clear:
This machine has become the single point of failure for your entire digital life.
Monitoring is no longer just a “cool dashboard.” It becomes the sentinel that watches everything for you when you are away from home. This guide walks through four monitoring options for ZimaCube, from lightweight to advanced.
Option 1: Uptime Kuma — Lightweight and Straightforward
Uptime Kuma is a lightweight service availability monitoring tool. What it does is simple: it regularly checks whether the services you specify are responding, and notifies you if they are not.

Installation, Docker or LXC
# Docker method, the simplest option
docker run -d \
--name uptime-kuma \
-p 3001:3001 \
-v uptime-kuma:/app/data \
louislam/uptime-kuma:latest
Configure Monitors
Open:
http://your-IP:3001
Then add monitors:
| Monitor Type | Target | Check Interval |
|---|---|---|
| HTTP(s) | https://192.168.1.100:8006, Proxmox | 60 seconds |
| Ping | Router IP | 30 seconds |
| TCP Port | Port 53 of the DNS server | 60 seconds |
| HTTP(s) | Health check endpoints of critical services | 60 seconds |
Notification Channels
Uptime Kuma supports dozens of notification channels, including Telegram, Email, Webhook, DingTalk, and Feishu. It is recommended to configure at least two: one for instant alerts, such as Telegram or Feishu, and one as a fallback, such as Email.
Uptime Kuma only tells you that something is down. It does not tell you why it is down. For a home environment, this is usually enough. Once you know something is down, you can SSH in and investigate.
Option 2: Pulse — Deep Integration With Proxmox
Pulse is a monitoring dashboard designed specifically for Proxmox and is installed as an LXC container. Compared with Uptime Kuma, which mainly tells you whether something is online, Pulse tells you how healthy the system is.

Installation
Pulse provides an LXC template, allowing you to create the container directly in Proxmox. Refer to the official Pulse documentation for installation steps.
Core Features
- Host overview: charts for CPU, memory, network, and disk usage
- Per-VM/CT details: resource usage of each individual virtual machine or container
- Backup status tracking: which VMs failed their last backup
- Active alerts: push notifications for CPU overload, disks nearing full capacity, or backup failures
A very real daily-use experience is this: every morning, you open Pulse, scan the status of three hosts in five seconds, and close it. You do not need to stare at a dashboard all day.
Option 3: Proxmox Data Center Manager — Multi-Host Management
If you have more than one Proxmox host, such as a ZimaCube plus an old Mac Mini or PC, Proxmox’s official Data Center Manager can help you manage multiple hosts in one place.
It provides:
- Cross-host metrics aggregation
- Unified storage pool view
- Real-time backup progress monitoring
The interface leans toward an enterprise style, with high information density and many charts. For a home setup with only one or two machines, Pulse already covers 90% of daily needs. The added value of Data Center Manager becomes more obvious when you have three or more hosts.

Option 4: AI Monitoring Agent — The Charm of Overengineering
This is the most “out there” option among the four, and also the one that feels the most futuristic.
The Idea
Instead of staring at a pile of dashboards and charts, let an AI Agent periodically SSH into your Proxmox hosts, check service status, and send you a natural-language summary:
“Everything looks normal today. ZimaCube’s average CPU usage is 12%, and memory usage is 45%. The backup completed at 03:07 and took 4 minutes. DNS response time is normal. One thing to note: NVMe cache pool usage has increased from 52% to 61% over the past week. At this rate, expansion may be needed in about 3 weeks.”
Implementation
Create an LXC container on ZimaCube, install Claude CLI or a similar AI tool, and write a cron script:
#!/bin/bash
Run every day at 8 AM and 8 PM
1. SSH into each host and collect command outputs such as qm list, pvesh, and zpool status
2. Feed the output to the AI Agent
3. Let the AI generate a summary and send it to Telegram or Feishu
ZimaCube has enough CPU and memory to run this AI Agent. A lightweight LXC container is enough.
Why It Is Not Recommended Yet
As proof of concept, this is interesting. But in daily use:
- Output quality is unstable, and the line between “everything is fine” and “something seems wrong” can be vague.
- When troubleshooting, you still need to open the terminal and check the raw data.
- Maintenance costs remain: AI API keys, model updates, and prompt tuning.
Put it on the “maybe try later” list. For now, the golden combination is Pulse + Uptime Kuma.
Recommended Combinations
| Your Scenario | Recommended Setup |
|---|---|
| Only one ZimaCube | Uptime Kuma |
| ZimaCube running Proxmox with 5+ VMs/CTs | Pulse + Uptime Kuma |
| Multiple Proxmox hosts | Pulse + Proxmox Data Center Manager |
| You enjoy tinkering and have time | Any of the above + try an AI Agent |
Monitoring Is Not the End Goal
Building this monitoring system brings an unexpected benefit:
In the past, you might occasionally wonder, “Are the backups running?” and then log in to check. Now, the system stays silent when everything is normal and only calls you when something goes wrong. That silence itself becomes a form of trust.
The time you invest in ZimaCube—installing Proxmox, configuring backups, and setting up monitoring—is essentially spent buying peace of mind.
A NAS gives you storage.
A server gives you capability.
A good monitoring system gives you the freedom to stop worrying.
Acknowledgment:
This article is based on the ZimaCube Experience Blog by community user Bob. Special thanks to Bob for his detailed Proxmox hands-on notes and sincere sharing.
Zima Campaign Hub
More to Read

From Sparcstation to ZimaBlade: A 57-Year-Old Geek’s Self-Hosting Journey
A French admin professional replaced his failed Raspberry Pi 4 with a ZimaBlade 7700, running Debian 13, XFS, and BorgBackup. Full backup server build...

ZimaCube vs DIY NAS: Which One Is Right for You?
Prebuilt NAS or DIY? We break down real costs, setup time, Thunderbolt 4, and maintenance differences to help you decide which build actually fits...

ZimaOS vs Proxmox vs Windows Server: Which System Should Your ZimaCube Run?
ZimaOS, Proxmox, and Windows Server each suit different users. Compare setup time, VM support, and use cases to pick the right OS for your...

