search

ethereum / glados

Portal network monitoring application.
60 stars 27 forks source link

Add Radius and "Should store" column in Audit page #161

Open kdeme opened 11 months ago

kdeme commented 11 months ago

The audit page is very useful to track how content is available over the network and how many hops are done for a recursive find content.

Now when a No Progress node occurs, it would be nice to know whether that node should have had the content or not.

I think that to achieve this we could add a radius column that could optionally be filled in if the Origin node happens to know the radius of the No Progress (or other) nodes. Additionally, the calculation, based on distance and radius of this node, can be done to see whether this node should store this content in theory. This could be indicated in another column, or perhaps be indicated with a color, e.g. marking the whole row red if it didn't have the content but should have had it.

Additional summaries could be made based on how many nodes failed to fulfill their task, etc.

I assume that the portal_historyTraceRecursiveFindContent call would need a slight adaptation to include the optional radius information.

edit: Actually, the information is equally useful for Responded nodes.

kdeme commented 3 months ago

Since there is the is-content-in-deadzone API since a while, a perhaps simpler option would be to have some special marking for any audit that failed and where the https://glados.ethdevops.io/api/is-content-in-deadzone/0x... returns no ENRs