[metrics-bugs] #23761 [Metrics/Website]: Add IPv6 relay graphs to metrics site

[Tor Bug Tracker & Wiki]

#23761: Add IPv6 relay graphs to metrics site
----------------------------------+------------------------------
 Reporter:  teor                  |          Owner:  metrics-team
     Type:  enhancement           |         Status:  new
 Priority:  Medium                |      Milestone:
Component:  Metrics/Website       |        Version:
 Severity:  Normal                |     Resolution:
 Keywords:  core-tor-wants, ipv6  |  Actual Points:
Parent ID:                        |         Points:
 Reviewer:                        |        Sponsor:
----------------------------------+------------------------------

Comment (by karsten):

 Replying to [comment:5 teor]:
 > I've cc'd isis, because they will have a better idea of which IPv6
 bridge stats would be useful. (I'd say "like the existing bridge stats",
 or "like the IPv6 relay stats", but I'd only be guessing.)

 Maybe we don't need isis for this, because there's really not much data
 available for bridges and IPv6. For example, the bridge authority does not
 confirm reachability of IPv6 OR ports, so we can only use what bridges
 announce in their descriptors. And neither relay flags like `Guard` or
 `Exit` have a meaning for bridges, nor have exit policies. We also have no
 consensus weights for bridges. And measuring advertised bandwidth of
 bridges does not make as much sense, because there's no load balancing in
 place for bridges like there is for relays.

 Basically, we only have "Total (IPv4) OR" and "IPv6 announced OR" for
 number of bridges supporting IPv6. Here they are together in a graph:

 [[Image(bridges-ipv6-2017-11-09.png, 700px)]]

 So, assuming these three graphs ("Number of relays supporting IPv6", Total
 advertised bandwidth by relays supporting IPv6", "Number of bridges
 supporting IPv6") are what we should add to Tor Metrics, would you mind
 suggesting some useful graph descriptions and other meta data? Basically,
 we'd need three new entries into [https://gitweb.torproject.org/metrics-
 web.git/tree/website/src/main/resources/etc/metrics.json this JSON
 document]. If nothing comes to mind, we'll make up something, but I
 believe descriptions will be better if they're at least based on your
 suggestions.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23761#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online