O4.2 Ensure Arti collects performance metrics and delivers them to the metrics pipeline
This ticket is a placeholder for all the tickets related to the activity 4.2 of objective 4 for project 141.
In this Activity we will make sure that Arti collects performance metrics and that these metrics are delivered and displayed to the public metrics portal (metrics.torproject.org) by ensuring Arti’s extra-info and metrics-port performance data is included in the metrics pipeline.
Specifically, we will ensure that Arti collects the same set of relevant network performance data as the C implementation and re-exports it to the existing metrics pipeline. (There is a small subset of usage metrics that are related to now-obsolete versions of the Tor protocols. Arti will not support these protocol versions so this information will not be collected and reported by Arti.)
The specific information to be collected is covered in the "extrainfo" document, which is specified in section 2.1.2 of dir-spec.txt
. In the C implementation, this information is exposed via the router_build_fresh_signed_extrainfo()
function, and collected in various function-specific cases throughout the codebase.
Just like in O4.1, the collection and performance reporting of metrics is critical to the success of the project. Without this information, we would not be able to report important statistics, such as the number of users on the network, the number of users visiting from various countries, the usage of various pluggable transports, and the prevalence of different protocols. We use this information to detect network trends and anomalies, which is extremely important during a migration such as the one planned in this project. Equally important, the M&E Plan of this project relies on this Activity. We cannot meaningfully report on our Objectives or measure our Indicators without this Activity.
Deliverable: metrics-port performance data for Arti.
- Estimation: 2 months for 1 person at 25% of their time
- Timeline: start on December 2024 and ends on March 2025
Next
-
Create tickets to complete this activity. -
Add tickets to this 'parent' ticket as "linked items". -
Estimate each of those tickets.