#26950 closed enhancement (implemented)

Remove "Fraction of relays reporting onion-service statistics" graph after August 15

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/Website Version:
Severity: Normal Keywords:
Cc: metrics-team, asn, dgoulet Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When we added graphs on onion services back in March 2015, we also included the "Fraction of relays reporting onion-service statistics" graph.

Back then, this graph was somewhat useful for pro users, to see how onion-service statistics deployment proceeded over time and to assess how much we could trust the overall numbers. However, since fractions went up to 50% in 2016 or even 75% in 2017, this graph has become less relevant.

Also, when we added this graph in 2015 we still had an "advanced/pro" category of graphs that were not displayed by default. We don't have that distinction anymore and simply throw everything we have at our users.

I suggest we remove this graph now from Tor Metrics. It costs maintenance effort, and it distracts our users from the more important graphs.

We could (should?) even keep providing the data by including a frac column in the CSV files linked from the other two onion-service graphs. That's how we do this with the user number graphs. If somebody wants to graph fractions of reported statistics, they can easily do that themselves using their favorite graphing tool.

Thoughts? Are there any good reasons to keep this graph?

Child Tickets

Change History (10)

comment:1 Changed 12 months ago by asn

Sounds good. I'm fine with killing it! Let's do it!

comment:2 Changed 12 months ago by karsten

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

Great, thanks for commenting! Leaving this ticket out here for a few more days, just in case anybody objects, and then killing the graph.

comment:3 Changed 12 months ago by irl

How much maintenance effort is it to keep the data in the CSV file? If we end up keeping the bulk of the code we could remove around, then I think we can just drop it. If it still allows us to remove the bulk of the code then I would prefer to keep a little effort to keep the frac there in the CSV. It could be the difference between us being very confused or very quickly being able to understand an event.

comment:4 Changed 12 months ago by karsten

Keeping the data in the two other per-graph CSV files (this and that) takes zero additional effort. We need to compute the numbers anyway. I'd say if we take out the fractions graph (this one) we should at the same time add the data to the other two graphs.

comment:5 in reply to:  4 Changed 12 months ago by irl

Replying to karsten:

Keeping the data in the two other per-graph CSV files (this and that) takes zero additional effort. We need to compute the numbers anyway. I'd say if we take out the fractions graph (this one) we should at the same time add the data to the other two graphs.

I like this.

comment:6 Changed 12 months ago by karsten

Status: acceptedmerge_ready

Okay, scheduled for August 15, together with the suggested changes to per-graph CSV files (#25383). Thanks!

comment:7 Changed 12 months ago by karsten

Summary: Remove "Fraction of relays reporting onion-service statistics" graphRemove "Fraction of relays reporting onion-service statistics" graph after August 15

comment:8 Changed 12 months ago by karsten

Status: merge_readyneeds_review

comment:9 Changed 12 months ago by asn

Status: needs_reviewmerge_ready

Commit looks reasonable.

comment:10 Changed 11 months ago by karsten

Resolution: implemented
Status: merge_readyclosed

Great, thanks for checking! Merged and deployed. Closing.

Note: See TracTickets for help on using tickets.