To show more info to users in the dashboard, we should add a disconnect_reason to probes, with a different value for each ProbeError (ip limit, asn limit, vpn, ...). The tricky part is getting the code to sync into the DB, since disconnected probes are not considered in sync. One option might be to add disconnected probes to an in-memory list that the sync process reads, and then use them (separately) in the existing match + update flow. It would be great if this not only updates existing probes but also creates new ones (maybe only if they have an adoption token to reduce "spaming" of the DB). The disconnect reason would then be cleared on any future update.
To show more info to users in the dashboard, we should add a disconnect_reason to probes, with a different value for each
ProbeError(ip limit, asn limit, vpn, ...). The tricky part is getting the code to sync into the DB, since disconnected probes are not considered in sync. One option might be to add disconnected probes to an in-memory list that the sync process reads, and then use them (separately) in the existing match + update flow. It would be great if this not only updates existing probes but also creates new ones (maybe only if they have an adoption token to reduce "spaming" of the DB). The disconnect reason would then be cleared on any future update.