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

Re: [tor-bugs] #21315 [Circumvention/Snowflake]: publish some realtime stats from the broker?



#21315: publish some realtime stats from the broker?
-------------------------------------+--------------------------------
 Reporter:  arma                     |          Owner:  cohosh
     Type:  enhancement              |         Status:  needs_revision
 Priority:  Medium                   |      Milestone:
Component:  Circumvention/Snowflake  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:  anti-censorship-roadmap  |  Actual Points:
Parent ID:  #29461                   |         Points:
 Reviewer:  irl                      |        Sponsor:  Sponsor28-can
-------------------------------------+--------------------------------
Changes (by cohosh):

 * status:  needs_review => needs_revision


Comment:

 Replying to [comment:31 irl]:
 Thanks irl!
 > Was there a reason for removing "snowflake-available-count"? This number
 is going to be the same as the sum of all country codes in "snowflake-
 ips", but it would probably be nice to have this in addition to be able to
 see at a glance.
 >
 I opted for `snowflake-idle-count` and `snowflake-client-match-count`
 instead, since I think this gives us the information we'd want to use
 `snowflake-available-count` for anyway. I'm not opposed to exporting
 another stat on the available snowflakes, I'll add the code for that back
 in shortly.

 > I can follow your thought processes and I think that these metrics
 described in comment:19, and also snowflake-available-count from
 comment:14 would be OK to make public. Nothing is jumping out as
 particularly sensitive.
 >
 > Is it possible to run two snowflake proxies from the same IP address?
 There does seem to be an implied limit of 1 proxy per IP address in your
 metrics descriptions. Maybe from a perspective of whether a bridge is
 burned or not, the fact that two processes may be running on the same IP
 doesn't matter because they would both be burned together?
 It is possible to run multiple snowflakes on a single IP. Only the country
 codes stats (and the total available snowflakes which I'll add back in)
 are unique by IP. The `snowflake-idle-count` and `snowflake-client-match-
 count` are not unique by IP and would reflect one IP address running
 multiple snowflakes. I think splitting the metrics in this way makes
 sense. The unique-by-IP ones will tell us information that's useful for
 censorship or blocking by IP and the ones that aren't unique by IP will
 tell us useful information about load on the system.


 I'm putting this back into needs_revision to add the total available
 snowflake stats. I'll get a code review on that once I complete it, and
 then I'm tempted to close out this ticket and open a new one for the next
 steps in hooking these metrics outputs to whatever the metrics team needs
 to publish these.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21315#comment:32>
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