[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]:
 > Hi Karsten, thanks, these look great!

 Great! And thanks for the detailed response below.

 > [...]
 >
 > I would like to see a relay counts by IPv6 announced OR / IPv6 confirmed
 OR / IPv6 exiting / total (IPv4) OR. It would seem to fit with the other
 graphs on the servers page of metrics. I want to have these numbers
 because they are a useful overview, and because they affect things like
 the size of the consensus.

 I guess that would be a graph like this:

 [[Image(relays-ipv6-2017-11-08.png, 700px)]]

 It contains the same data as the long graph above.

 > I would also like to see advertised bandwidth by confirmed guard IPv6 OR
 / confirmed middle IPv6 OR / confirmed exit IPv6 OR / IPv6 exiting / total
 (IPv4) OR. This could go with the other graphs on the traffic page of
 metrics. I want to have these numbers because they show us how easy it is
 for clients to use IPv6 to get in and out of the Tor Network, and they can
 help us decide when we can use more IPv6 between relays. (I don't want to
 graph observed bandwidth until we start logging separate IPv4 and IPv6
 stats on ORPorts and exits, because I think it would be confusing.)

 This one was a bit harder:

 [[Image(advbw-relays-ipv6-2017-11-08.png, 700px)]]

 The five lines in these graph are:

  - Total (IPv4) OR: Total advertised bandwidth of all running relays in
 the network, so far so good.
  - Confirmed guard IPv6 OR: Total advertised bandwidth of all running
 relays with a confirmed reachable IPv6 OR address and with the `Guard`
 flag.
  - Confirmed middle IPv6 OR: Total advertised bandwidth of all running
 relays with a confirmed reachable IPv6 OR address and with neither `Guard`
 nor `Exit` flag.
  - Confirmed exit IPv6 OR: Total advertised bandwidth of all running
 relays with a confirmed reachable IPv6 OR address and with the `Exit`
 flag.
  - IPv6 exiting: Total advertised bandwidth of all running relays with a
 configured IPv6 exit policy that is not `reject *:*`.

 Note that these lines are not independent. If suddenly a bunch of relays
 with confirmed reachable IPv6 OR addresses and with both `Guard` and
 `Exit` flag show up, the guard and exit lines will go up, even though
 clients will prefer them for either position based on the current Wxx
 bandwidth weights. I'm not trying to make this more complex than
 necessary. But maybe there's a way to pick slightly different set of lines
 that don't have this issue? Or maybe it's "just" a question of writing
 good enough documentation.

 > 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.)

 I'm curious! I'll hold back making graphs until I know what would be most
 useful.

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