wiki:org/teams/MetricsTeam

Version 111 (modified by karsten, 10 months ago) (diff)

Add two more ticket numbers.

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

March 15, 2018 Onionoo 5.1-1.11.0, cf. announcement downloads
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
No tickets found

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; 50% of 50% 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; 95% 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; 100% done)
  1. Extend Onionoo to use JNDI for rDNS lookups (M; 100% done)

Visualizations
  1. Add OONI graphs to Tor Metrics based on pre-aggregated data from vanilla Tor test and bridge reachability test (M; 45% done)
  2. Add IPv6 relay graphs to Tor Metrics based on existing descriptor contents (M; 100% done)
  1. 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; 100% of originally planned 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; 100% done)
  3. Help the Core Tor and Tor Browser teams with ongoing measurements (M; 100% done)
About
  1. Document the Tor Metrics system/pipeline, including explicitly writing down our requirements (Sponsor 13) (4/5 L; 20% of originally planned 10% done, deferred)

Burndown Chart

Draft roadmap from October 2018 to March 2019

In Mexico City, we started a draft roadmap for the time until March 2019. The following tasks are still subject to change.

  1. Extend OnionPerf to measure performance of Tor with mobile networks and/or PTs (requires #26673). (2M, Sponsor 19)
  2. Rewrite CollecTor relaydescs module using Stem/txtorcon, at least consensuses and server descriptors as proof of concept (#28320). (2M, Sponsor 13)
  3. Write technical report documenting the metrics code base, the CollecTor prototype, the OONI comparison, and recommendation (#25644). (M, Sponsor 13)
  4. Evaluate at least one other (not MaxMind) GeoIP database that could be used to improve data analysis and visualisation within Tor Metrics. (S)
  5. Review information architecture for Tor Metrics (#24422) and update to Bootstrap 4. (M)
  6. Write an initial CollecTor module for PrivCount including format specification discussions. Make some internal graphs (not on Tor Metrics) with: number of relays supporting each statistics version in each consensus; number of relays actually reporting statistics in each day; number of tally reporters processing statistics. (M)
  7. Finish operational issues notifications (#28322). (M; 30% done)
  8. Add a metrics-web module to add the consensus weight per bwauth graph from #25459. Requires using votes in metrics-web. (M; 100% done)
  9. Run arthur's DNS timeout scanner, archive it in CollecTor, and add it to Onionoo. (2M)
  10. Finish OONI vanilla Tor data. (M, Sponsor 19)
  11. Create an additional information lookup service using remote APIs (RIPEstat) and local databases (MaxMind). Consider adding back the relays by country graph to Tor Metrics. (2M)
  12. Finish having 2 operators for each service (#28327). (S)
  13. Make a plan for adding external research data to either Tor Metrics or the research portal. (S; 15% done)
  14. Rewrite or extend TorDNSEL with Stem to support IPv6. (2M)
  15. Extend dir-spec to serve recent, non-current consensuses and votes (#21378) and CollecTor to fetch them (#28324). Requires help by the network team. (M)
  16. Review CollecTor's use of file system storage and explore alternatives, potentially ZFS. (M; 10% done)
  17. Finish adding Java 8 date/time (#23752). (M)
  18. Add sbws data to CollecTor (#21378) and to Onionoo (#28321). (M)
  19. Improve the graph from #25459. (S)

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Summary Component Status Owner Priority Severity Created Modified Reporter
#19332 Add a BridgeDB module Metrics/CollecTor assigned karsten Medium Normal 3 years ago 4 hours ago mrphs
#29655 Tor Metrics / Users / Bridge users by country and transport / Source: China, fails to render graph lines clearly Metrics reopened metrics-team Medium Normal 7 months ago 4 hours ago monmire
#31755 Separate update pings and update requests graphs for Tor Browser alpha and release users Metrics/Website new metrics-team Medium Normal 13 hours ago 13 hours ago boklm
#29461 Add a Snowflake module Metrics/CollecTor merge_ready metrics-team Medium Normal 7 months ago 14 hours ago irl
#31714 Update instructions for enabling javascript when javascript is disabled Metrics/Relay Search new metrics-team Medium Normal 5 days ago 5 days ago boklm
#31558 Process bridge pool assignments again Metrics/CollecTor needs_review metrics-team Medium Normal 3 weeks ago 5 days ago karsten
#31695 Allow pushing Metrics to CollecTor from trusted endpoints Metrics/CollecTor new metrics-team Medium Normal 6 days ago 6 days ago irl
#24434 Provide fallback list parser Metrics/Library new metrics-team Medium Normal 22 months ago 8 days ago iwakeh
#30636 Something funky is going in Iran: numbers of relay users flies off to 1M+ Metrics/Analysis new metrics-team Medium Normal 4 months ago 8 days ago cypherpunks
#31649 Add ant task in metrics-base to fetch metrics-lib/exonerator from dist Metrics new metrics-team Very Low Normal 11 days ago 11 days ago irl
#31599 Create utility class for downloading from HTTP servers Metrics/CollecTor new metrics-team Medium Normal 2 weeks ago 2 weeks ago karsten
#31521 Investigate 10-second delay in TTFB Metrics/Analysis new metrics-team Medium Normal 3 weeks ago 3 weeks ago karsten
#31204 Extend file objects in index.json to include descriptor types, publication times, and file digests Metrics/CollecTor accepted karsten Medium Normal 2 months ago 3 weeks ago karsten
#31481 Hidden service v3 @type Metrics/Website new metrics-team Low Minor 4 weeks ago 3 weeks ago atagar
#31435 Emulate different Fast/Guard cutoffs in historical consensuses Metrics new metrics-team Medium Normal 4 weeks ago 4 weeks ago irl
#31439 Identify poorly performing relays from historical OnionPerf data Metrics/Analysis assigned karsten Medium Normal 4 weeks ago 4 weeks ago irl
#31438 Provide a Java application to exclude "impossible" paths from OnionPerf results given an alternate consensus Metrics/Analysis new metrics-team Medium Normal 4 weeks ago 4 weeks ago irl
#31437 Provide a tunable Java implementation of consensus generation Metrics/Analysis new metrics-team Medium Normal 4 weeks ago 4 weeks ago irl
#31436 Provide a tunable Java implementation of vote generation Metrics/Analysis new metrics-team Medium Normal 4 weeks ago 4 weeks ago irl
#31434 Write ANTLR parsers for dir-spec descriptors and benchmark Metrics/Library new metrics-team Medium Normal 4 weeks ago 4 weeks ago irl
1 2 3 4 5 6 7 8 9 10 11

Attachments (12)

Download all attachments as: .zip