[ ] make a command line tool to receive a "dat address" as an argument and return "the health" either as a one time snapshot or allow to subscribe to continuously receive updates.
"dat address" (can be for hypercores, hyperdrives, hypertries, etc...)
the meaning of "the health" depends on what you think we can get:
e.g. how many hypercores are involved (e.g. hyperdrives have 2)?
e.g. how many peers participate in the swarm?
e.g. what is the throughput (download) possible?
e.g. how often is each chunk duplicated?
e.g. what is the fluctuation of peers?
e.g. what is the latency for particular chunks?
e.g. etc...
[ ] additionally it would be cool to support also kappa-* stuff if that's possible :-)
if i'm not mistaken kappa still uses hypercores underneath it all
Of course we wan't it modular, so we can re-use individually the logic to figure out from a "dat address" whether we are dealing with a hypercore, a hyperdrive, a hypertrie or something else.
We want to be able to listen to the module to keep on receiving data about the health and we might want to store the history, so when we ask the command line tool for the same address, it already has some historical data.
Any feedback or suggestion for how to approach this or do it maybe even differently are welcome :-)
@todo"dat address"as an argument and return"the health"either as a one time snapshot or allow to subscribe to continuously receive updates."the health"depends on what you think we can get:kappa-*stuff if that's possible :-)Of course we wan't it modular, so we can re-use individually the logic to figure out from a
"dat address"whether we are dealing with a hypercore, a hyperdrive, a hypertrie or something else. We want to be able to listen to the module to keep on receiving data about the health and we might want to store the history, so when we ask the command line tool for the same address, it already has some historical data.Any feedback or suggestion for how to approach this or do it maybe even differently are welcome :-)