[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #21047 [Metrics/Onionoo]: atlas plotting bandwidth use from 2019

#21047: atlas plotting bandwidth use from 2019
-----------------------------+------------------------------
 Reporter:  arma             |          Owner:  metrics-team
     Type:  defect           |         Status:  new
 Priority:  Medium           |      Milestone:
Component:  Metrics/Onionoo  |        Version:
 Severity:  Normal           |     Resolution:
 Keywords:  metrics-help     |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:                   |        Sponsor:
-----------------------------+------------------------------
Changes (by karsten):

 * keywords:   => metrics-help
 * owner:  irl => metrics-team
 * component:  Metrics/Atlas => Metrics/Onionoo


Comment:

 Good catch!  This issue is caused by the relay reporting bandwidth
 statistics for 2019 and Onionoo not discarding those from bandwidth docs
 until it's 2019.

 I'd rather want us to fix this in Onionoo, not in Atlas and all other
 Onionoo clients.

 Example descriptor `6/3/63ff123399bafc9b28d837ea0fa63f798c4a6a2a` from
 [https://collector.torproject.org/archive/relay-
 descriptors/consensuses/consensuses-2016-08.tar.xz this tarball]:

 {{{
 @type extra-info 1.0
 extra-info ibibUNC0 7C0AA4E3B73E407E9F5FEB1912F8BE26D8AA124D
 identity-ed25519
 -----BEGIN ED25519 CERT-----
 AQQABqUhAdjBLiDAqJkCFA78jFKmtyEcvi7nN00//KSYCoKpE6TzAQAgBACXy4i0
 fCVhw8iXMdARg94Jrxgv1VrBYtDp9Ak4uNJ/lxDHI5ZZpFJcPy4MttbTR2sOfQSV
 Z69+66RK+u6BAbJhJyuxOaShT2LcjHYbdaGaUbjGzyRHJu4vdg9sxvcMqQY=
 -----END ED25519 CERT-----
 published 2016-08-02 10:10:33
 write-history 2019-08-07 05:31:45 (14400 s) 0,0,0,0,0,0
 read-history 2019-08-07 05:31:45 (14400 s) 0,0,0,0,0,0
 dirreq-write-history 2019-08-07 07:30:55 (14400 s) 0,0,0,0,0,0
 dirreq-read-history 2019-08-07 07:30:55 (14400 s) 0,0,0,0,0,0
 geoip-db-digest 6346E26E2BC96F8511588CE2695E9B0339A75D32
 geoip6-db-digest 43CCB43DBC653D8CC16396A882C5F116A6004F0C
 dirreq-stats-end 2016-08-01 18:06:45 (86400 s)
 dirreq-v3-ips be=8,de=8,es=8,fr=8,us=8
 dirreq-v3-reqs us=16,be=8,de=8,es=8,fr=8
 dirreq-v3-resp ok=16,not-enough-sigs=0,unavailable=0,not-found=0,not-
 modified=0,busy=0
 dirreq-v3-direct-dl complete=0,timeout=0,running=0
 dirreq-v3-tunneled-dl
 complete=16,timeout=0,running=0,min=214075,d1=214075,d2=572799,q1=600118,d3=600118,d4=655941,md=1484660,d6=1494430,d7=1681836,q3=1683076,d8=1683076,d9=1708236,max=1920647
 hidserv-stats-end 2016-08-01 18:06:45 (86400 s)
 hidserv-rend-relayed-cells 739 delta_f=2048 epsilon=0.30 bin_size=1024
 hidserv-dir-onions-seen 121 delta_f=8 epsilon=0.30 bin_size=8
 router-sig-ed25519
 BzxV6kj3qhd/Gr7yoTGc+ExAC81XIN27wZrOzZf+Gw2Wohkg8b3wd3FoB/K5tBDlEz2nqsR11RiS+Hmd0n1gDQ
 router-signature
 -----BEGIN SIGNATURE-----
 QS+GfL/DC9cGrNdXHn4Maqzn5WiNdinO/6zIYhVXrApwwOTSpK3+phHLaTXyTz4m
 XB1LSLZI7/zZTl6ZIV0hvAPs4OzM2QKjQ1ss0cf7jRc2Ubq8LPROT1wO6kUY8Klj
 f0QcrdoQkhVRCcOQ6HkJMbupLhfLnMJ9iDBBjD7ErDI=
 -----END SIGNATURE-----
 }}}

 With the analysis above I'd say that this ticket is a fine candidate for a
 new volunteer.  Fixing this issue could start with writing a test that
 uses the descriptor above as input and produces a bandwidth document until
 2019.  The next step would be to fix the issue.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21047#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs