Professor
ProfessorI am interested in seeing that KB guide if you're willing to share. Great rundown of the issue. Perhaps reducing the DS sample frequencies may help alleviate some of the issue for now. We're an MSP, so we're monitoring and taking action on alerts. We'll be able to advise the client to change any configurations/architecture, but not make any direct changes they don't approve.
I'm going to keep fiddling with the DataSources and their AppliesTo to see if I can reduce the amount of traffic... I've already done so by changing the AP one:
from:
hasCategory("Ubiquiti_Unifi") || (unifi.user && unifi.pass)
to:
hasCategory("Ubiquiti_Unifi") || (unifi.user && unifi.pass)
&& hasCategory("UbiquitiUnifiAP")
There are PropertySources that are tagging devices, but those properties aren't being used in the appliesTo to reduce the amount of Active Discovery queries against devices that wouldn't respond to them correctly anyway, causing timeouts rather than returns.
ProfessorFound a good reference for OIDs to help differentiate between device types... the AP PropertySource is already using this to do so: mibs.observium.org/mib/UBNT-MIB/
AP is looking for "1.3.6.1.4.1.41112.1.6.3.3.0"
I may clone the AP PropertySource and add a switch/case statement to find/select other device types to tag so they can be used in the appliesTo for the other PropertySources.
