Opened 9 years ago

Closed 7 years ago

#2931 closed enhancement (wontfix)

Extend metrics database schema to bridge descriptors

Reported by: karsten Owned by:
Priority: Low Milestone:
Component: Metrics/Website Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


The current metrics database schema contains relay descriptors with all their details and aggregate statistics on bridges, Torperf, and GetTor.

We should extend the schema to contain bridge descriptors with all their details, too, so that we can add new statistics on bridges more easily. Right now, adding new statistics means changing the Java code and parsing all bridge descriptors again. Possible new bridge statistics are number of bridges on hour detail, relay flags, Tor versions, and operating systems of bridges. We could also add bridge pool assignments to the database schema.

(Extending the database schema for Torperf and/or GetTor is probably not as useful: the Torperf data can still be processed without database support, and the raw GetTor data is already aggregated to protect the privacy of GetTor users.)

Child Tickets

Change History (4)

comment:1 Changed 9 years ago by karsten

One thing to consider here is that we'll have to re-implement the logic which bridge stats are included in the daily bridge user estimates. Right now the daily user estimates are calculated in Java, but once the data is in the database, we'll want to implement this in PL/pgSQL.

comment:2 Changed 9 years ago by karsten

Component: MetricsMetrics Website

comment:3 Changed 8 years ago by karsten

Owner: karsten deleted
Priority: normalminor
Status: newassigned

Nice to have, but huge effort for relatively little gain. Reducing priority to minor and unassigning myself.

comment:4 Changed 7 years ago by karsten

Resolution: wontfix
Status: assignedclosed

This seemed like a good idea 3 years back. But the current approach in metrics-web is that separate modules generate aggregate statistics and write results to .csv files. It's entirely up to the module whether they use a database for this task. That makes this ticket not relevant anymore. Closing.

Note: See TracTickets for help on using tickets.