We recently installed a UDM Pro to complete our Unifi network installation. To our surprise, this network equipment doesn’t have SNMP. So I’ve installed check_mk_agent from OpenWRT into this machine and most of it is working fine. But the process list is not working.
The output is broken because ps arguments are very limited on this device.
Could someone explain the expected output of <<>> section so I can adapt the OpenWRT agent to this Unifi Dream Machine ?
I tested this with the UniFi Controller Version 6.2.26 and a UAP-nanoHD AccessPoint. It works fine. There is a little problem with the naming for the uptime service which collides with the checkmk builtin Uptime service if you additionally use SNMP to request data from the AccessPoint.
Hello, I don’t think you need an SNMP check, just create your access point as a host in checkmk exactly as it says in Unifi, without an agend, just with the option “Use piggyback data from other hosts if present (default value)”
Tomorrow I can test this additionally with a unifi switch.
I’ve got also a USG, but I don’t want to use it anymore. So if someone is searching for one… tell me.
I would not recommend to rename this check if it does show the same value as the snmp uptime.
Better solution would be to use the “supersedes” feature at registering the agent section.
Something like this here.
register.agent_section(
name = 'unifi_device',
parse_function = parse_unifi_dict,
supersedes=["snmp_uptime"],
)
I don’t know superseed. But let’s talk about two situations.
one does not use SNMP
In this case you have the uptime information from piggyback (everything is cool)
one uses SNMP additionally
a. without renaming or using superseed us run into problems
BUT
if you want to use parameters on uptime like “Minimum required uptime” or “Maximum allowed uptime” you will not finde those in the piggybacked service
The parameter problem is clear if i look at the code of the check.
It is a little bit strange how it is build
If the check would create a real uptime check then you could also use the rule.
But this check has no parameters und uses a service description with empty string and item “Uptime”, that’s really strange.
This whole check must be rewritten to build clean checks with parameters. At the moment it is nearly impossible to have parameters there.
@Doc sorry still not enough time to look through. Saw your PR.
wouldnt it be much easier to just change that uptime is no longer listed under <<<unifi_device:sep(124)>>> but instead just as normal <<>>
Then there is no need for snmp uptime to set parameter