wiki:org/teams/MetricsTeam

Version 95 (modified by karsten, 2 months ago) (diff)

Update roadmap progress.

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 14:30 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 Metrics Team is not 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' 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 20, 2017 Onionoo 5.0-1.9.0, cf. announcement downloads
November 28, 2017 Onionoo 4.4-1.8.0, cf. announcement downloads
November 20, 2017 Onionoo 4.3-1.7.1, cf. announcement, preparing major version jump downloads
October 27, 2017 Joint release of milestones CollecTor 1.4.1, Onionoo 4.2-1.6.1, cf. announcement downloads
October 10, 2017 Joint release of milestones CollecTor 1.4.0, metrics-lib 2.1.1, Onionoo 4.2-1.6.0, cf. announcement downloads
September 15, 2017 Joint release of milestones CollecTor 1.3.0, metrics-lib 2.1.0, Onionoo 4.1-1.5.0, cf. announcement downloads
August 31, 2017 milestone Onionoo 4.1-1.4.0 and 4.1-1.4.1 announcement download Onionoo 4.1-1.4.1
August 18, 2017 announcement download CollecTor 1.2.1
August 8, 2017 milestone Onionoo 4.0-1.3.0 download Onionoo 4.0-1.3.0
July 13, 2017 milestone CollecTor 1.2.0 download CollecTor 1.2.0

older Metrics releases

Planned Milestones

CollecTor 1.5.0 CollecTor 2.0.0
metrics-lib 2.2.0 metrics-lib 3.0.0
ExoneraTor 1.0.0 ExoneraTor 2.0.0
MetricsWeb 1.0.0 MetricsWeb 2.0.0
Onionoo 2.0.0 Onionoo 2.1.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.

More documentation

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
#27723 Obfs4 stopped working 16 Sept 18 new Medium Normal mwolfe 5 days ago
#26807 Venezuela blocks access to the Tor network new Medium Normal ptdetector 2 months ago
#26087 Growth in bridge users in Iran circa 2018-05-01 new Medium Normal cypherpunks 4 months ago
#20348 Allot Communications blocking of vanilla Tor, obfs4, and meek in Kazakhstan, starting 2016-06 reopened Medium Normal dcf 5 months ago
#25966 Report on Tor in the UAE (and question about Snowflake) new Very Low Trivial mwolfe 5 months ago

Roadmap from October 2017 to September 2018

We put together a roadmap for 2017/18 in Berlin in September 2017, refined it at the Tor meeting in Montreal in October 2017, and updated it at a team-internal meeting in Aberdeen in April 2018. The following contains a very short version of goals for the time until September 2018 and will be updated over time:

Short-term goals (Q4/2017)

Code
  1. Update all code to use Java 8 features (M; 30% of 30% done, deferred)
  2. Switch ExoneraTor and metrics-web from Tomcat to embedded Jetty, and harmonize directory structures (M; 100% done)
Operation
  1. Deploy better notification system for operational issues (M; 30% of 30% done, deferred)
  2. Make sure that each service has at least two operators (M; 30% done)
Sources
  1. Add web server logs as new data source (M; 100% done)
News
  1. Provide metrics timeline events as both a table on Tor Metrics pages and as an RSS/Atom feed that is also syndicated via Twitter to increase community engagement (M; 60% done)
Services
  1. Make Atlas part of the Tor Metrics website (M; 100% done)
  2. Make Compass part of Atlas in order to provide aggregated search results and details pages on Atlas and to finally shut down Compass (M; 100% done)
  3. Resolve ExoneraTor database slowness (M; 25% of 25% done, deferred)
  4. Extend Onionoo to use JNDI for rDNS lookups (M; 80% done)

Visualizations
  1. Add OONI graphs to Tor Metrics based on pre-aggregated data from vanilla Tor test and bridge reachability test (M; 40% done)
  2. Add IPv6 relay graphs to Tor Metrics based on existing descriptor contents (M; 100% done)
  3. Add a few more performance graphs based on existing OnionPerf data (M; 100% done)
About
  1. Rename Tor Metrics components to make them easier to understand for people outside of the team (M; 45% of 45% done, deferred)

Medium-term goals (until Q3/2018)

Research
  1. Document aggregated statistics files better (Sponsor 13) (8/5 L; 50% of 80% done)
  2. Put external research data on the website, including Rob's phantomtrain OnionPerf data and Yixin's BGP monitoring data (M; 30% done)
Sources
  1. Re-process bridge descriptor tarballs to retain “contact” lines in server descriptors and “fingerprint” lines in statuses (M; 25% of 25% done, deferred)
  2. Support PrivCount development and integrate its data as successor to statistics reported by relays and bridges (M; 80% done)
  3. Help the Core Tor and Tor Browser teams with ongoing measurements (M; 80% done)
About
  1. Document the Tor Metrics system/pipeline, including explicitly writing down our requirements (Sponsor 13) (4/5 L; 10% of 80% done)

Burndown Chart

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 248)

1 2 3 4 5 6 7 8 9 10 11
Ticket Summary Component Status Owner Priority Severity Created Modified Reporter
#21933 Fix deserialization of UTF-8 characters in details statuses and documents Metrics/Onionoo new metrics-team Medium Normal 18 months ago 3 days ago karsten
#27746 Compile slide deck to present Tor Metrics for the open day session in Mexico Metrics accepted irl Medium Normal 6 days ago 6 days ago irl
#23913 Allow parameters and qualified search terms to be specified more than once Metrics/Onionoo assigned metrics-team Medium Normal 11 months ago 7 days ago nusenu
#27715 support relative time in timestamp parameter Metrics/ExoneraTor new metrics-team Medium Normal 8 days ago 7 days ago exonerator
#27714 support more recent lookups Metrics/ExoneraTor new metrics-team Medium Normal 8 days ago 7 days ago exonerator
#27716 Out of memory when loading in multiple years of relay descriptors Metrics/CollecTor new metrics-team Medium Normal 8 days ago 7 days ago irl
#27390 Properly clean up sanitized web server logs in the recent/ directory Metrics/CollecTor merge_ready metrics-team Medium Normal 3 weeks ago 10 days ago karsten
#26767 add consensus weight line/graph Metrics/Relay Search new metrics-team Medium Normal 2 months ago 11 days ago nusenu
#27572 metrics.tpo glossary bandwidth terms Metrics/Statistics new metrics-team Medium Normal 2 weeks ago 11 days ago juga
#19650 Keep non-printable characters out of details documents Metrics/Onionoo assigned metrics-team Medium Normal 2 years ago 3 weeks ago cypherpunks
#27187 Possible for inconsistency between summary and details with AS number Metrics/Onionoo new metrics-team Medium Normal 5 weeks ago 4 weeks ago irl
#27235 add route_origin_rpki_validity field Metrics/Onionoo new metrics-team Medium Normal 5 weeks ago 5 weeks ago nusenu
#26585 improve AS number and name coverage (switch maxmind to RIPE Stat) Metrics/Onionoo new metrics-team Medium Normal 3 months ago 5 weeks ago nusenu
#27155 Include BGP prefix information in details documents Metrics/Onionoo new metrics-team Medium Normal 5 weeks ago 5 weeks ago nusenu
#27181 Avoid unnecessary disk writes Metrics/Onionoo new metrics-team Medium Normal 5 weeks ago 5 weeks ago irl
#24870 Use java 8 date-time functionality in Onionoo Metrics/Onionoo new metrics-team Medium Normal 8 months ago 5 weeks ago iwakeh
#27154 Do not display "AS0" in results or details pages Metrics/Relay Search accepted irl Medium Normal 5 weeks ago 5 weeks ago nusenu
#27153 add ipv6_as and ipv6_as_name Metrics/Onionoo new metrics-team Medium Normal 5 weeks ago 5 weeks ago nusenu
#26863 display onionoo and RS version on RS pages Metrics/Relay Search reopened metrics-team Medium Normal 2 months ago 6 weeks ago nusenu
#27138 display timestamp and version information on page with no results Metrics/Relay Search accepted irl Medium Normal 6 weeks ago 6 weeks ago nusenu
1 2 3 4 5 6 7 8 9 10 11

Attachments (10)

Download all attachments as: .zip