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.
ProfessorI've also found a note in the description of the DSs indicating that past a certain point, the API won't work for them:
If anyone on the module dev team is looking in here, is this on the roadmap to get updated?
