LibreNMS and Oxidized by cloudimg
by cloudimg
Network monitoring and configuration backup on one VM, already integrated
Two tools that run a network, as one product
LibreNMS is an auto discovering network monitoring system. Point it at a switch, router, firewall, server or PDU and it finds the interfaces, sensors and services by itself, keeps the history and draws the graphs. It covers what network teams actually chase: interface throughput and errors, BGP and OSPF sessions, VLANs, wireless clients, temperature and power, across several hundred device families.
Oxidized is its natural counterpart. It logs into each device, retrieves the running configuration and commits it to a git repository, so every change is visible as a diff and any previous version can be restored.
Why they are better together
On this image they share one inventory and one interface. Oxidized takes its entire device list from LibreNMS, so the devices you already monitor are the devices that get backed up, and there is no second list to keep in step. In the other direction, LibreNMS is configured to read from Oxidized, so each device's saved configuration and its full version history appear on that device's Config tab inside the LibreNMS web interface. You add a device once, in one place, and both jobs start.
It works the moment it boots
Most monitoring products cannot show you anything until you have pointed them at your own equipment. This one monitors itself. On first boot the VM configures its own SNMP agent, registers itself as a monitored device and runs a real discovery and poll, so the first page you sign in to already shows a live host with real graphs, and Oxidized has already taken and committed a configuration backup of it. You can see exactly how the product behaves before you touch your own network.
Secure by default
No usable credential ships in the image. On first boot the VM generates its own database password, application key, administrator password, SNMP community, API token and the SSH key used for configuration collection, all unique to that machine and written to a root only file.
The SNMP agent and the Oxidized API both listen on the loopback interface only and are never reachable from the network, because the Oxidized API has no authentication of its own and an exposed SNMP community is worth having. LibreNMS's authenticated web interface is the single front door and serves the configuration views itself. The account used to read this appliance's own configuration is a separate, key only, password locked account restricted to loopback connections.
What you get
- LibreNMS and Oxidized pinned to vetted upstream releases, integrated in both directions
- nginx, PHP 8.3 FPM, MariaDB, RRDtool with rrdcached and Net SNMP, configured and enabled
- Self monitoring from first boot: a real device, a real poll, real graphs and a real configuration backup
- Every secret generated per VM on first boot, with no default login anywhere in the image
- Memory tuned to run the whole stack inside 4 GiB with no swap, and unattended security upgrades left enabled
Licensing
LibreNMS is published under the GNU General Public License version 3.0 and Oxidized under the Apache License 2.0. Both are free and open source, with no licence fee and no key to enter. cloudimg is not affiliated with either project. The cloudimg charge ($0.04 per vCPU/hour) covers packaging, security patching, image maintenance and 24/7 expert support.