Hi all, I’ve been using Observium for the last year or so to monitor my home network. It has worked pretty OK, but for a number of reasons I am looking at deploying LibreNMS instead. I have stood up an Ubuntu LibreNMS installation (from “scratch”), and am working through Dan’s migration scripts.
Most things are migrating OK, but there are a few discrepancies. For some devices, memory, storage, and port RRDs are only going back to LibreNMS installation, while others like processors, uptime, etc go all the way back to Observium installation. For other devices, the ports data goes back to Observium installation, but not all the ports are present.
Is there a way to see what is and isn’t being used in addhost.php, and to massage the RRDs so that my historical data gets brought over properly?
I don’t might blowing away LibreNMS data or the whole installation and trying again; I am leaving Observium running in parallel. until I am satisfied with my LibreNMS setup.
If I /opt/librenms/delhost.php <hostname> and then convert just that one host over, I get a different set of RRDs that populate all the way back to Observium installation vs just back to LibreNMS /opt/librenms/addhost.php <hostname>. Doesn’t seem to be deterministic.
Addhost.php does nothing to migrate the data, it simply creates a new host in LibreNMS. When the poller runs, it renames the Observium rrd files. Make sure you have the Observium rrds in place before running addhost so the poller doesn’t run first.
Yup, I have checked that. The migration scripts copy the XML dumps over, restore them with rrdtool, chown to librenms:librenms, and only after all of that is addhost.php called.
Looking at the log page for the device, the poller renames port-x.rrd to port-idy.rrd for each of the discovered ports (I guess matching on the port association mode), but is not doing any renames for the other missing RRDs like memory and storage. Does the poller make any attempt to try to identify and map existing non-port RRDs?
I suppose I could manually try to figure out which Observium file names match to which LibreNMS file names, and change those before calling addhost.php; that sounds like it would take some work
Possibly; I expect most of them are, though. I’m taking a look right now at comparing what Observium has, what LibreNMS has if I just add the device with no migration, and what LibreNMS has if I do the migration.
Yup. When I first started working on the migration, I didn’t recall if Observium had been running in a 32-bit or 64-bit VM. I’ve stuck with the XML conversion since that’s what I was working on; I only have a handful of devices, so the conversion is not onerous. Although I should double-check that I am seeing the same behavior with and without XML conversion.
We don’t actually migrate any rrd files from observium, at one stage we both still used the same formats. We’ve updated our port ones to a new format but try and detect this and convert. I guess they’ve moved to a new format for other graphs.
If someone can give us the file name format they use we might be able to build in detection to pick these up and rename.
