Getting data from the peoplesopen.net/monitor

[eenblam]

What data can we get now?

What improvements could be made to the monitor in terms of data retention, API endpoints, etc?

What can we visualize locally in the repo with the data available / potentially available?

[eenblam]

cc @bennlich

[bennlich]

👋 @eenblam

We're currently storing:

• for each exitnode, the most recent time a routable subnet appeared in its routing table, and the associated gateway (this is what gets rendered in the giant tables at the bottom of https://peoplesopen.net/monitor)
• for each exitnode, a dump of its routing table every ~2 minutes. One entry looks like:

{
  timestamp,
  exitnodeIP,
  routes: [ { nodeIP, gatewayIP }, ... ]
}

nodeIP above is really a subnet address. This data currently gets rendered as both the network topology and the timeseries plot. We only render the last 24 hours of data, but we store the most recent 200MB, which is somewhere between 1 month and 1 week's worth of entries.

--

Some data we could derive from the above:

• average number of nodes connected to the mesh in the last ~month
• stability of a specific node in the last ~month (e.g. how many times it disconnected and reconnected)
• most popular exitnode
• newest node IPs that joined the mesh

--

We could go further back in time either by increasing the storage limit, or by storing derived values we are interested in instead of entire routing table dumps.