Given the possibility of issues with getting the primary/wireless IP address from the API results (e.g. https://github.com/aredn/aredn/issues/758), the poller/collector should capture the IP address used to make a request and store that in the node table (a new connection_ip column?).
Having this address could also be used for resolving topology links to nodes in the database.
I have some other ideas about cleaning up the code for the collector/poller, which I think this is probably a good opportunity for:
Push results onto one or more deques instead of using gather() (looking ahead to Python 3.11's task groups). Multiple deques could be used to categorize successful results from errors.
Given the possibility of issues with getting the primary/wireless IP address from the API results (e.g. https://github.com/aredn/aredn/issues/758), the poller/collector should capture the IP address used to make a request and store that in the
node
table (a newconnection_ip
column?).Having this address could also be used for resolving topology links to nodes in the database.
I have some other ideas about cleaning up the code for the collector/poller, which I think this is probably a good opportunity for:
gather()
(looking ahead to Python 3.11's task groups). Multiple deques could be used to categorize successful results from errors.