Improving monitoring OpenWrt with Checkmk

Community Builds, Projects & Packages
1

I want to improve monitoring with Checkmk and need some input.

First: The current set of services that are generated by the agent script is very minimal. Mostly CPU load, storage occupation and network interfaces. I think at least installed packages (to detect manipulation) and number of WiFi devices connected would be helpful. But I am also open to diving a bit deeper into security related stuff, just give me hints.

The current state as a typical router looks in the monitoring:

openwrt_cmk23
openwrt_cmk231188×765 117 KB

Another topic will be packaging and making the agent Luci configurable. But later... Anyway, if you have hints, I am glad to get links.

Disclaimer: I am employed at Checkmk GmbH, but this currently is my spare time project.

2 Likes
2

conntrack "connections" are more important.
in old "swconfig" still current on ath79 platform network ports hide behind switch and are no netdevs.
mostly documented here

or for other sided approach

ubus -v list

"connected device" has a very loose definition, it is dhcp client vs wifi association.

Bit counters are wildly delayed with firewall offloads, wire bits via ethtool are often better.

You are welcome either way.

1 Like