What this guide covers
WatchZit is a free, open-source (AGPLv3) monitoring system for networks and servers. Its centre is the network map: devices with real pictures and ports, cables that show their traffic, everything coloured by its state. Behind the map are the checks, graphs and alerts you know from tools like Zabbix. It runs on one small Linux server or as a ready-made virtual machine, with no per-device price and no cloud.
What you need
- A virtual machine on VMware, Proxmox VE or Hyper-V with 2 CPUs, 2 GB of memory and a 16 GB disk — or any 64-bit Debian 12+, Ubuntu 22.04+, AlmaLinux or Rocky Linux 9+ server. That is enough for a few hundred devices.
- SNMP on the devices you want to see in detail (MikroTik, Cisco, HP, Ubiquiti, printers, UPSs …): a v2c community or a v3 user that may only read.
- For MikroTik routers with RouterOS 7, optionally the www or www-ssl service and a user in a read-only group, for the RouterOS API check.
Install the server
The quickest way is the appliance: a ready-made image with Debian, WatchZit, PostgreSQL and automatic security updates. Download it from the download page — OVA for VMware ESXi and Workstation, qcow2 for Proxmox VE and KVM, VHDX for Hyper-V (generation 1) or an ISO for a new VM or a physical server — import it, start it and follow the menu on its screen. It shows the console address and the setup token.
On a Linux server of your own, one command as root does the same:
curl -fsSL https://github.com/Max-Zit/watchzit/releases/latest/download/install.sh | sudo sh
The script installs PostgreSQL, checks the signature of the release, creates the database with a random password, opens the ports and starts the service. At the end it prints the console address and the setup token. Running it again later updates WatchZit.
First sign-in
- Open
https://<server>:8443. The browser warns once about the self-signed certificate; accept it. - Enter the setup token and create the first administrator.
- Scan the QR code with an authenticator app — two-factor sign-in is required — and keep the recovery codes.
The console answers only to private networks by default. Keep it that way; agents, if you use them later, need only port 8444.
Find the devices of a network
Like The Dude's discovery, Devices → Discovery scans a range such as 192.168.88.0/24 (up to a /22, now, every day or every week). WatchZit pings every address, tries common ports (SSH, Telnet, web, RDP, WinBox, SMB, printers, VNC), asks SNMP with your SNMP profiles for the name, description and maker, and looks up the DNS name. Tick the hosts you want and add them; each new device gets a ping check.
A single device is added under Devices with just a name and an address.
Read MikroTik devices: SNMP and the RouterOS API
- On the router, turn SNMP on (
/snmp set enabled=yes) and set a community that may only read — or a v3 user with SHA-2 and AES, which WatchZit supports. - In WatchZit, create the profile under Settings → SNMP and choose it on the device. SNMP discovery opens: tick the interfaces, CPU, memory and disks to watch. Loopbacks and interfaces without link are left out.
- The device page now shows the ports with their link state and live traffic, and graphs of every value from an hour to a year.
For RouterOS 7, add the check MikroTik RouterOS (API) as well: it reads CPU, memory, uptime and temperature over the REST API, and with it WatchZit reads the bridge VLANs, VXLAN tunnels and VRRP state of the router. MikroTik's neighbour discovery, LLDP and CDP tell WatchZit which port is plugged into which — the basis for the map.
Under Configuration backups WatchZit can also save the RouterOS export every night over SSH and show what changed between two versions.
Draw the map
Under Maps, add a map and click Edit.
- Add device puts devices on the map. Every device gets a picture — from the built-in library of some 3,500 real models, MikroTik routers and switches with their ports included, or one you upload.
- Suggested links lists the cables WatchZit found from neighbour tables, the MAC address tables of switches and port descriptions, with the ports at both ends. Add all takes them. With Draw by itself the map keeps adding new links and the devices they lead to every 15 minutes.
- Arrange lays the map out by its cables: the router on top, the switches below it and what hangs on them below those.
- Click Save.
Green is up, amber partly down and red down. Cables get wider and change colour with their traffic, and a port without link is drawn red and dashed. Click a device for its checks and ports, a cable for its traffic history. Racks, VLAN filters, the path between two devices, submaps and hypervisor boxes with their virtual machines are there when the network grows. For a monitoring TV, Settings → Kiosk displays shows maps full screen behind a secret link.
Alerts
Built-in triggers already watch for devices that are down, packet loss, high CPU load, full disks and expiring certificates. Set up where problems go under Settings → Notifications: email, webhook, Slack or Microsoft Teams. Dependencies keep the noise down — when the router of a branch office is down, you get one problem, not one per device behind it — and maintenance windows and acknowledgements do the rest.
Open WinBox, SSH and web pages from the map
A device's panel opens its web page, SSH, Remote Desktop, WinBox or your own tools with one click. The programs on your computer are started by the small MaxZit Launcher, which you install once from the console, and it opens WinBox with the address of the router.
The Dude and WatchZit side by side
| The Dude | WatchZit | |
|---|---|---|
| Server | A RouterOS package (older versions also on Windows) | Linux server or ready-made VM image |
| Client | A Windows program | Any browser, in 14 languages |
| Maps | Devices, links and submaps | Real device pictures with ports, racks, VLANs, VXLAN, HA groups, hypervisors, links found by themselves |
| Beyond the map | Probes and their graphs | SNMP, agent, web, database and API checks, two years of history, dashboards, reports, roles with two-factor and single sign-on, an audit log |
| Price | Free | Free and open source (AGPLv3), paid support if you want it |
The Dude remains a good tool for a MikroTik-only network. WatchZit is for networks of several makers, for servers and services next to the routers, and for teams that want to work in a browser.
What to do next
- Install the agent on Windows and Linux servers for CPU, memory, disks, services and event logs (documentation).
- Put a remote collector in each branch office: it runs the checks of its site and keeps measuring when the line to the console is down.
- Build a dashboard for the wall screen and a monthly availability report.
Questions and ideas are welcome in GitHub Discussions (English only).
MikroTik, RouterOS, WinBox and The Dude are trademarks of their owner. MaxZit is not affiliated with, sponsored or endorsed by the owner of these names; they are used only to describe what this guide is about.