Opened 7 months ago

Last modified 5 weeks ago

#29112 new enhancement

PTs should pass user count events back to Tor

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.4.2.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 041-deferred-20190530, network-team-roadmap-october
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor: Sponsor28-can

Description

Right now relays and bridges publish aggregate per-country stats in their extrainfo descriptors, like

dirreq-v3-ips us=5768,ru=1952,id=1584,de=912,in=696,[...]

(And in the future they will add noise to them in a smarter way, like via privcount, but that's orthogonal to this ticket.)

It would be great to have per-transport stats to go with this data.

One approach would be for the PT to send back an event when it hears about a user, or when a user does a countable thing like fetching a consensus. And then Tor can aggregate them according to however it thinks is best.

(We could have the PT do the aggregation, but (a) teaching the PT about geoip lookups when it otherwise doesn't need them doesn't sound so fun, and (b) teaching each PT how to add noise appropriately seems like it scales poorly compared to doing it once, well, inside Tor.)

Related question: what stats does https://metrics.torproject.org/userstats-bridge-transport.html use currently?

This ticket motivated by #29111.

Child Tickets

Change History (8)

comment:1 Changed 7 months ago by ahf

Would the following two messages help here:

  1. STATUS TYPE="client_connect" IP=<IPv4/IPv6 IP> SOURCE_PORT=1234
  2. STATUS TYPE="client_disconnect" IP=<IPv4/IPv6 IP> SOURCE_PORT=1234

Optionally the "client_disconnect" message could include how much traffic that was received/send to the given client.

comment:2 Changed 4 months ago by nickm

Milestone: Tor: 0.4.1.x-final

Tentatively placing this in 0.4.1, but please remove if it isn't important or there isn't time.

comment:3 Changed 4 months ago by nickm

Sponsor: Sponsor19-can

comment:4 Changed 3 months ago by nickm

Keywords: 041-deferred-20190530 added

Marking these tickets as deferred from 041.

comment:5 Changed 3 months ago by nickm

Milestone: Tor: 0.4.1.x-finalTor: 0.4.2.x-final

comment:6 Changed 3 months ago by gaba

Keywords: ex-sponsor-19 added

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

comment:7 Changed 3 months ago by phw

Sponsor: Sponsor19-canSponsor28-can

Moving from Sponsor 19 to Sponsor 28.

comment:8 Changed 5 weeks ago by gaba

Keywords: network-team-roadmap-october added; ex-sponsor-19 removed
Points: 1
Note: See TracTickets for help on using tickets.