Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
Description
I have used Observium at work, and have been trying to utilizing it as much as possible in my homelab. I am using Entware, on various systems, more than Debian, or RedHat Linux distributions. I had wish to monitor software packages managed by Entware and were installed on my devices. As Observium already had the majority of this functionality, with dpkg, I made the following necessary adjustments for it to work with opkg as well. opkg package files have the ipk file extension.
Apart from the 10 or so seconds it takes to create the $opkgFile, I have not observed, and this should not, under normal circumstances, have a significant performance impact.
From a security-monitoring standpoint this may be instrumental in identifying software versions, and/or when they were upgraded on a system.
package-poller.patch
Fetches <<<opkg>>> data from the unix-agent and adds, or updates, them in Observium's DB.
In order to keep similarity to dpkg, it casts the package size, to integer.
package-page.patch
Displays ipk packages with label-info style.
agent-opkg.patch
The script that runs locally on the device. As the dpkg script, it caches the results for 30 minutes.
If a package is installed offline (ipk {}file), rather than from a repository, opkg info will only show size of the package from the repository.
Example for device with opkg only
Example for device with dpkg and opkg.