Perform one-off analysis for number of relays a bwauth decided the median for

Having some graphs for all-time, last year and maybe last month or so would be cool. Thanks!

added component::metrics/analysis metrics-2018 owner::tom priority::high resolution::fixed severity::normal status::closed type::defect labels

I put a sample graph on #21882 (moved), because there were lots of good thoughts on making such a graph. Please take a look there. Once we have a graph we're happy with, I'll make one for a few months of data (which takes a while).

So for the historical bwauth measuring graphs - I think i will generate historical data for them... What i do currently is place data into a sqlite database, and then every hour export the most recent 90 days worth of data in a csv for javascript graph generation. I think I will backfill the database... so I ought to be able to generate some one-off graphs like the ones you created showing historical data.

I'm wondering if/what is the best approach to let my consensus-health graphs get configurable and usable in metrics.tpo

Trac:
Status: new to assigned
Owner: metrics-team to tom

Replying to tom:

So for the historical bwauth measuring graphs - I think i will generate historical data for them... What i do currently is place data into a sqlite database, and then every hour export the most recent 90 days worth of data in a csv for javascript graph generation. I think I will backfill the database... so I ought to be able to generate some one-off graphs like the ones you created showing historical data.

That would be neat!

I'm wondering if/what is the best approach to let my consensus-health graphs get configurable and usable in metrics.tpo

Fine question! There's no easy answer, because so far we don't use externally provided .csv files for graphs on Tor Metrics. But I could imagine doing this in the future, if the data reaches back to more than the past 90 days (ideally a few years back when bandwidth authorities became a thing). We could simply fetch the .csv files as part of the cronjob that generates .csv files. Though I'd say, for now, let's start with the graphs on consensus-health.tpo and see if they're as useful as we hope. If they are, let's have this discussion again!

I have created a first draft of the historical graphs here, covering 90, 180, 365, and 720 days: https://ritter.vg/misc/bwauth-historical/graphs-historical.html

If these graphs are useful enough (for now) this can be the final draft until.... I expect that I will be making interactive graphs that enable historical analysis also, so feedback on how these graphs look will guide into that.

Trac:
Status: assigned to needs_information

Adding a verb to the summary to make this ticket "actionable". Speaking of, what remains to be done here?

Trac:
Summary: One-off analysis for number of relays a bwauth decided the median for to Perform one-off analysis for number of relays a bwauth decided the median for

I don't think anything needs to be done, unless Sebastian or Karsten or anyone has comments about the graphs (either the look or questions about the data.) Although it's been a while since I generated them so I will need to relearn what I did ;)

Trac:
Keywords: N/A deleted, metrics-2018 added

Trac:
Keywords: metrics-2018 deleted, metrics-2017 added

Will be completed in 2018.

Trac:
Keywords: metrics-2017 deleted, metrics-2018 added

Adding metrics-team to cc

Trac:
Cc: N/A to metrics-team

Changing priority to high to finally get this resolved soon.

Trac:
Priority: Medium to High

Replying to tom:

I don't think anything needs to be done, unless Sebastian or Karsten or anyone has comments about the graphs (either the look or questions about the data.) Although it's been a while since I generated them so I will need to relearn what I did ;)

Nothing to be done here. The historical graphs look good, and I just checked that there are current ones on Consensus Health. Closing this ticket. If anybody has ideas for making them better, they're likely going to open a new ticket anyway. Thanks!

Trac:
Resolution: N/A to fixed
Status: needs_information to closed

closed