Add new document type with monthly relay and bridge statistics to Onionoo
Last week, I talked to Torservers people about generating reports on total traffic relayed by a relay or average number of users of a bridge (related to #10331 (moved)). I suggested using the data contained in Onionoo's bandwidth documents and yet-to-be-implemented clients documents and aggregating them by month.
While this approach is certainly doable, it has the downside that Onionoo's graph data becomes less detailed over time. Which is okay for graphs, but not nice if one wants a report for 12 or 24 months ago. Also, it's not exactly trivial to transform data from the current format to monthly intervals.
Here's another approach: Onionoo could serve another document which aggregates statistics by month, regardless of how long observations lie in the past. Each data point would start on the first day of a month at 00:00 UTC and end on the last day of the month at 23:59 UTC, except for the first and last data point.
Possible data for this new document type:
- Bandwidth: how many bytes did the relay or bridge write and read in a month? The document would say when the relay showed up first (which was probably not exactly on the first day of a month at 00:00 UTC), and it would say until when in the current month bandwidth data has been included. Would be available for relays and bridges, though it's probably more important as a success metric for relays than for bridges.
- Uptime: what fraction of known network statuses contained the relay or bridge with the Running flag? Would be available for relays and bridges.
- Clients: how many users did the bridge have on average when it reported client statistics? Also, what countries did users come from (only listing countries with at least 1% of users of this bridge), what transports did they use (only included if reported), and what IP versions did they use (only included if reported)? Would only be available for bridges, because directory mirrors and directory guards make it impossible to get these data for single relay.
(We'll want to create three or more child tickets if we agree that this new document type would be useful.)
Would this new document type be useful for Torservers people?