wiki:org/teams/MetricsTeam

Version 53 (modified by iwakeh, 17 months ago) (diff)

added collector 1.1.2

Metrics Team

Overview

Welcome to the Metrics Team page. The Metrics Team is a group of Tor people who care about measuring and analyzing things in the public Tor network. There are currently three other teams in Tor: the Network Team writes the software to keep the Tor network running, the Applications Team produces usable applications for end users, and the Community Team focuses on the non-technical aspects of growing a healthy Tor community. But if you're interested in measurements and analyses, the Metrics Team is what you're looking for. Welcome!

People

The Metrics Team currently consists of between half a dozen and a dozen developers, depending on how and when you count. We're not listing names here to keep the team open to everyone. You're on the team if you're participating in discussions and development, and you're not part of the team anymore if you decide you want to move on (which we hope won't happen).

Communication

Our synchronous medium of communication is IRC meetings that happen every Thursday at 15:00 UTC in #tor-dev on OFTC.

If you want to reach someone from the team between these meetings to ask a development-related question, just go to #tor-dev and mention the magic word "metrics", and somebody from the team might either be around or appear later and get back to you.

Our asynchronous medium of communication is the metrics-team@ mailing list. This list is public in the sense that anyone can subscribe and read archives. But it's moderated on first post, meaning that your first post will be reviewed to make sure it's not spam and on topic and all further posts will go directly to the list. Feel free to subscribe and just listen if you want, and feel free to post if you have a question that you think is on topic.

Products

The MetricsTeam is no selling any products, don't worry.

Product is a codebase of software maintained by the Team. Not all products of the Metrics Team are mentioned in this section (for a more complete list see roadmap draft). Instead, we list some long-term products here that are or will be released in way that a third party can decide to run a mirror of this type of service.

Here some links to these products' wiki development pages (in alphabetical order):

  • CollecTor the friendly data collecting service. A wiki subsection for CollecTor mirror operators mirror operating wiki.
  • ExoneraTor helps to find out whether that address was used as a Tor relay.
  • Metrics the primary place to learn interesting facts about the Tor network.
  • metrics-lib a Java library that fetches and parses Tor descriptors.
  • Onionoo is a web-based protocol to learn about currently running Tor relays and bridges. A wiki subsection for Onionoo mirror operators mirror operating wiki

Releases and Milestones

Releases

December 5, 2015 download metrics-lib 1.0.0
December 28, 2015 download metrics-lib 1.1.0
May 31, 2016 download metrics-lib 1.2.0
July 7, 2016 download metrics-lib 1.3.0
August 1, 2016 download metrics-lib 1.3.1
August 11, 2016 milestone CollecTor 1.0.0 download CollecTor 1.0.0
August 22, 2016 bugfix for #19913 download CollecTor 1.0.1
August 31, 2016 milestone metrics-lib 1.4.0 download metrics-lib 1.4.0
October 7, 2016 milestone CollecTor 1.0.2 download CollecTor 1.0.2
October 19, 2016 milestone metrics-lib 1.5.0 download metrics-lib 1.5.0
October 28, 2016 milestone CollecTor 1.1.0 download CollecTor 1.1.0
November 23, 2016 milestone Onionoo 3.1-1.0.0 download Onionoo 3.1-1.0.0
November 24, 2016 milestone CollecTor 1.1.1 download CollecTor 1.1.1
January 17, 2017 milestone CollecTor 1.1.2 download CollecTor 1.1.2

Planned Milestones

CollecTor 1.2.0 CollecTor 2.0.0
metrics-lib 1.6.0 metrics-lib 2.0.0
ExoneraTor 1.0.0 ExoneraTor 2.0.0
MetricsWeb 1.0.0 MetricsWeb 2.0.0
Onionoo 3.1-1.1.0 Onionoo 3.1-2.0.0

Documentation

An FAQ by and about the Metrics Team. If something you want to know is not answered yet, check back in a few days. Or address your question directly to us via the communication channels listed in the previous section.

The 32C3 State of the Onion talk covered work of the Metrics Team by giving example of how bad relays are detected, investigated, and excluded from the Tor network. The entire talk is worth watching, but if you're short on time, be sure to watch minutes 20 to 28.

A concise description of all Metrics products is under way.

Censorship Watch

MetricsTimeline lists incidents that might help in interpreting metrics graphs.

Here's a table with tickets related to censorship incidents:

Ticket Summary Status Priority Severity Reporter Modified
No tickets found

Roadmap from October 2016 to June 2017

The metrics team put together the following roadmap for the time from October 2016 to June 2017. This list was created for the Seattle meeting in September 2016 and will be updated on a regular basis and revisited at the next meeting around March 2017.

  • 2016-10: Provide user-friendly documentation that empowers users to independently operate CollecTor instances. (Sponsor X 1.2. CollecTor)
  • 2016-10: Enable CollecTor to synchronize Tor network data from other CollecTor instances. (Sponsor X 1.3. CollecTor)
  • 2016-10: Set up a second CollecTor instance and enable synchronization with the first CollecTor instance. (Sponsor X 1.4. CollecTor)
  • 2016-11: Define a release process for Onionoo and put out at least one release. (Sponsor X 3.1. Onionoo)
  • 2016-11: Provide user-friendly documentation that empowers users to independently operate Onionoo instances. (Sponsor X 3.2. Onionoo)
  • 2016-12: Conduct a usability analysis of the current Tor Metrics website to identify the most pressing usability issues. (Sponsor X 6.1. Metrics)
  • 2016-12: Compare the Tor Metrics website code to RStudio's Shiny Server and other web frameworks. (no specific sponsor)
  • 2017-01: Perform an analysis on reducing the amount of sensitive, potentially personally identifying data stored in memory of Tor relays and bridges or reported to the directory authorities. (Sponsor X 4.1. Tor daemon)
  • 2017-01: Add a visualization of Tor Browser downloads to Metrics. (Sponsor X 6.3. Metrics, part 1)
  • 2017-01: Finalize visualizations of Tor Browser downloads on Metrics based on user feedback. (Sponsor X 6.3. Metrics, part 2)
  • 2017-02: Replace all existing Torperf instances gathering current Tor network performance measurements with OnionPerf instances. (Sponsor X 5.1. OnionPerf)
  • 2017-02: Improve usability of the most pressing issues identified in the earlier usability analysis as long as they are within scope to make it easier for users to find, compare, and interpret Tor usage and performance metrics. (Sponsor X 6.2. Metrics)
  • 2017-03: Write an outline of further improvements or prototypes for all metrics-related Java products. (no specific sponsor)
  • 2017-04: Develop and deploy at least one more user model in addition to the current model. (Sponsor X 5.2. OnionPerf)
  • 2017-04: Reduce the amount of sensitive, potentially personally identifying data stored in memory of Tor relays and bridges by implementing at least one suggestion from the earlier analysis document. (Sponsor X 4.2. Tor daemon)
  • 2017-04: Obfuscate data that gets reported by Tor relays and bridges to the directory authorities by implementing at least one suggestion from the earlier analysis document. (Sponsor X 4.3. Tor daemon)
  • 2017-05: Improve all usability issues of Atlas that are classified as High priority or above in the issue tracker as long as they are within scope and reported at least six months before the end of the award. (Sponsor X 3.3. Atlas)
  • 2017-06: Write user-friendly tutorials for metrics-lib/DescripTor that empower users to independently analyze large amounts of network data. (Sponsor X 2.3. metrics-lib/DescripTor)
  • 2017-06: Make a wider audience aware of the Tor descriptor parsing library metrics-lib/DescripTor by writing a blog post about it that explains how to use it. (Sponsor X 2.1. metrics-lib/DescripTor)

Open Tickets

The following table lists all open tickets, from recently modified to not touched in years, of products that are maintained by Metrics Team people or otherwise related. Not all of these products are actively maintained, so be sure to reach out to the team before starting to hack on any of these and also take a look at the Volunteer's Guide. Also note that not all metrics-related tools use Tor's Trac as their bug tracker, so you might also want to ask for bug trackers of other metrics tools.

Results (1 - 20 of 261)

1 2 3 4 5 6 7 8 9 10 11
Ticket Summary Component Status Owner Priority Severity Created Modified Reporter
#25774 Record latency measurements using OnionPerf Metrics/Ideas needs_review metrics-team Medium Normal 2 months ago 3 days ago irl
#21378 Archive bwauth bandwidth files Metrics/CollecTor new metrics-team Low Normal 17 months ago 6 days ago tom
#22026 Create new service to retrieve raw documents Metrics/Ideas new metrics-team Medium Normal 14 months ago 10 days ago irl
#21087 Separate truncated descriptor(s) from next complete descriptor Metrics/CollecTor accepted wulder Medium Normal 18 months ago 13 days ago atagar
#26124 Bring​ back Tor​ Weather Metrics new metrics-team Medium Normal 5 weeks ago 2 weeks ago nusenu
#25383 Deprecate stats.html and stats/*.csv files Metrics/Website assigned metrics-team High Normal 4 months ago 4 weeks ago karsten
#26193 Tarballs are not compressed in a run following an aborted run Metrics/CollecTor needs_review karsten Medium Normal 4 weeks ago 4 weeks ago karsten
#26171 Explain which cells are counted for onion service traffic graphs Metrics/Statistics assigned metrics-team Medium Normal 5 weeks ago 4 weeks ago teor
#25644 Write white paper about CollecTor's data processing (Sponsor13, 1) Metrics/CollecTor assigned metrics-team Medium Normal 3 months ago 4 weeks ago iwakeh
#26035 Streamline sample quantile types used in the various modules Metrics/Statistics needs_revision karsten Medium Normal 7 weeks ago 4 weeks ago karsten
#26132 Fix the Expires header on relay search Metrics/Onionoo assigned metrics-team Medium Normal 5 weeks ago 4 weeks ago teor
#25403 Create jsp with bgp documentation Metrics/Website needs_revision metrics-team Medium Normal 4 months ago 4 weeks ago iwakeh
#20224 Fix `BridgeDescriptorMappingsLimit` config option Metrics/CollecTor assigned metrics-team Low Normal 21 months ago 4 weeks ago karsten
#20351 Turn the updateindex module into a function that runs after each module run Metrics/CollecTor assigned metrics-team Medium Normal 21 months ago 4 weeks ago iwakeh
#25444 Add Apache Commons Codec dependency for java 9 Metrics/Library new metrics-team Medium Normal 4 months ago 4 weeks ago iwakeh
#20350 Replace create-tarball.sh shell script with Java module Metrics/CollecTor assigned metrics-team Medium Normal 21 months ago 4 weeks ago iwakeh
#26190 Use slf4j throughout all stats modules Metrics/Statistics new metrics-team Medium Normal 4 weeks ago 4 weeks ago iwakeh
#25358 Add a tutorial for new LogDescriptor, i.e., WebServerAccessLog reading Metrics/Website new metrics-team Medium Normal 4 months ago 4 weeks ago iwakeh
#23421 Use persistence functionality throughout all modules Metrics/CollecTor assigned metrics-team Medium Normal 10 months ago 4 weeks ago iwakeh
#25307 Use `persist` package for writing bridge descriptors in sanitization module Metrics/CollecTor assigned metrics-team Medium Normal 4 months ago 4 weeks ago iwakeh
1 2 3 4 5 6 7 8 9 10 11

Attachments (7)

Download all attachments as: .zip