Opened 2 years ago

Closed 2 years ago

#21760 closed enhancement (implemented)

Onionperf deployment - CollecTor side

Reported by: iwakeh Owned by: iwakeh
Priority: Medium Milestone: CollecTor 1.3.0
Component: Metrics/CollecTor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

This covers all CollecTor code base related topics for the introduction of onionperf measurements (see #21272).

Open is the addition of tests and the final move to OnionPerf only.

Child Tickets

Change History (5)

comment:1 Changed 2 years ago by iwakeh

During the team meeting we had the following question:
How could 'buggy' data be removed again fro CollecTor? Should we have this option?

These questions might translate into marking the file contents with their source, which could be done by CollecTor (pre-pending a line to the file contents).

Other suggestions?

comment:2 Changed 2 years ago by iwakeh

Milestone: CollecTor 1.3.0

comment:3 Changed 2 years ago by iwakeh

Owner: changed from metrics-team to iwakeh
Status: newaccepted

comment:4 Changed 2 years ago by iwakeh

Status: acceptedneeds_information

Is there anything left to be done?

comment:5 Changed 2 years ago by iwakeh

Resolution: implemented
Status: needs_informationclosed

As the switch to onionperf is done (cf. https://collector.torproject.org/recent/torperf/) and all remaining tasks (like sync and persistence etc.) have their own tickets, closing as implemented.

Note: See TracTickets for help on using tickets.