You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently store statistics about the number of probes over time, as well as details of adopted probes, but when non-adopted probes disappear, it's hard to identify what happened and why. I'm thinking it would make sense to sync all probes with the DB, not just the adopted ones so that we have more visibility into the network.
Non-adopted probes wouldn't have a user assigned which would require updating all parts of the code to handle that case. @alexey-yarmosh wdyt?
The text was updated successfully, but these errors were encountered:
Sync mechanism may be relatively easy updated to handle all probes. Existing table will store all probes and userId will be the indicator of adoption. Load will not increase a lot, cause big amount of probes is already adopted. Adoption mechanism also needs to be updated, but nothing significant.
We currently store statistics about the number of probes over time, as well as details of adopted probes, but when non-adopted probes disappear, it's hard to identify what happened and why. I'm thinking it would make sense to sync all probes with the DB, not just the adopted ones so that we have more visibility into the network.
Non-adopted probes wouldn't have a user assigned which would require updating all parts of the code to handle that case. @alexey-yarmosh wdyt?
The text was updated successfully, but these errors were encountered: