The UDT poller considers failed polling as having no data, causing the count of ports in use, IP, and MAC data to be all set to zero. It ignores any dependency checking in this process. This causes 'gaps' in the data returned and a large amount of unnecessary churn on the UDT data tables as MAC and/or IP address are removed from being 'active'
This can be seen in the output below for one of my (legacy) routers with 334 routed interfaces. On occasions when it is busy it doesn't return its ARP data fast enough, in that case all data is ignored and it sets the ports used to zero and removes the thousands of IP and MAC addresses from currently in use leading to graphs looking like this:
Idea:
1. UDT L2 polling should only update the port information if all of the port data has been returned
2. UDT L2 polling should only update the MAC information if all of the bridge data has been returned, otherwise it should not update anything
3. UDT L3 polling should only update the IP information if all of the ARP data has been returned, otherwise it should not update anything