metrics: interpretation, hierarchies and organisation

[dpaez]

This can include:

• [x] download
  • [ ] interpret the data sources we have (hypercore, hyperdrive.stat and hyperdrive.stats)
  • [ ] decide which data source is the more accurate (and when?) and organise it accordingly for display
• [x] upload
  • [ ] interpret the data sources we have (hypercore, hyperdrive.stat and hyperdrive.stats)
  • [ ] decide which data source is the more accurate (and when?) and organise it accordingly for display
• [ ] seed ratio
• [x] disk usage
• [x] cpu usage
• [x] uptime
• [x] peers available
• [x] network indicator
• [x] swarm stats

[dpaez]

Partially done with #21.

We still need to separate host resources stats from hyperdrive stats.

[dpaez]

Currently metrics are associated with a key and timestamp and saved into the local metricsDB. And there is an API endpoint that allows some basic queries.

[dpaez]

Some better organization and code cleaning added with #58 And network indicator added with #59