Opened 6 years ago

Closed 3 months ago

#6855 closed enhancement (fixed)

Support aggregation by tor version (exact and match on first three numbers)

Reported by: cypherpunkx Owned by: metrics-team
Priority: Low Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords:
Cc: gsathya, nusenu@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The metrics page shows [1] the number of relays running different versions of tor (0.2.1, 0.2.2, ...) over time. It would be nice to know what portion of the overall traffic is handled by which tor version. I could see this feature in two different granularities:

  • group relay versions based on the first three numbers (like [1] does)
  • group relay versions based on exact matches (example: 0.2.2.38 != 0.2.2.39)

[1] https://metrics.torproject.org/network.html#versions

Related feature requests:
#6662
#6675

Child Tickets

Change History (11)

comment:1 Changed 6 years ago by cypherpunkx

Summary: group by tor version (exact and match on first try numbers)group by tor version (exact and match on first three numbers)

comment:2 Changed 6 years ago by karsten

Cc: gsathya added
Priority: normalminor

I'm almost inclined to say that we should turn down this feature request, but I'm yet undecided.

If we add grouping by version, we'll also have to add a new version column to both command-line and website output. The next logical step would be to allow filtering by version, so that users can further investigate a certain version group. And if we do this all for versions, why not add OSes, too? And what's next?

The main focus of Compass was to investigate the Tor network for diversity and to keep track of the fast exits funding project. Making Compass a useful tool for community managers (which is the purpose here, right?) would be nice, too, but we shouldn't let that change the focus too much.

I'm putting this ticket into minor priority for now. Also cc'ing Sathya to hear his opinion.

comment:3 Changed 6 years ago by cypherpunkx

#6947 inspired me add the following variant of this feature request:

group by recommended version: show how much traffic is handled by relays running one of the versions included in the recommended versions (consensus) vs. not recommended versions

comment:4 Changed 3 years ago by tyseom

Cc: nusenu@… added

comment:6 Changed 7 months ago by karsten

Severity: Normal
Summary: group by tor version (exact and match on first three numbers)Support grouping by tor version (exact and match on first three numbers)

Tweak summary a bit.

comment:7 Changed 7 months ago by karsten

Owner: set to metrics-team
Status: needs_reviewassigned

comment:8 Changed 5 months ago by irl

Component: Metrics/CompassMetrics/Atlas

In #23517 it is planned to merge Compass functionality with Relay Search (formerly known as Atlas). These tickets may be relevant to that work and so these are being reassigned to the Metrics/Atlas component.

comment:9 Changed 3 months ago by irl

Summary: Support grouping by tor version (exact and match on first three numbers)Support aggregation by tor version (exact and match on first three numbers)

Rewrite summary to explain how this would be implemented in Relay Search.

comment:10 Changed 3 months ago by irl

As a compromise, I'm implementing basic aggregation (top-level only, not as part of a drill down) for version number based on the first 3 numbers. If there is interest in a more featureful aggregation with version numbers then this could be a new ticket. This ticket is 5 years old and was not even originally for Relay Search, so hopefully this implementation provides enough to be useful and also enough to understand better what is really needed from Relay Search now.

comment:11 Changed 3 months ago by irl

Resolution: fixed
Status: assignedclosed

Fixed in ba625b4.

Note: See TracTickets for help on using tickets.