Opened 2 years ago

Last modified 9 months ago

#26767 new enhancement

add consensus weight line/graph

Reported by: nusenu Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Relay Search has two graphs showing bw history data and relative values (fraction and probabilities):

  • consensus weight fraction
  • middle probability
  • guard probability
  • exit probability
  • written bytes per second
  • read bytes per second

One of the most relevant question for a relay operator is:
How is my relay doing?
Is it doing better or worse than usually?

A good data point to answer this is to look at the cw value over time (not cw fraction) since the probabilities and fraction values are relative and not directly controllable by the operator (i.e. other operators add relays).

This will allow relay operators to answer questions like:
"My cw fraction decreased, was it because my cw decreased or did my cw remain stable and someone else added more resources?"

a graph showing the ratio between cw fraction to cw would also be nice since it answers above question more directly without having to compare the cw and cw fraction lines manually

onionoo data:

the onion box displays a cw graph:

Child Tickets

Change History (4)

comment:1 Changed 2 years ago by irl

I am starting to think this is a nice replacement for the bandwidth graph in terms of giving an absolute number over time, for when we remove the per-relay bandwidth statistics reporting (see PrivCount work if this is surprising to you).

comment:2 Changed 17 months ago by irl

Keywords: metrics-roadmap-2019-q3 added

We should move this into the Metrics roadmap, even if we don't show it yet it would be good to have the graph ready for when bandwidth graphs go away.

comment:3 Changed 9 months ago by gaba

Releasing tickets from 2019 roadmap into the universe.

comment:4 Changed 9 months ago by gaba

Keywords: metrics-roadmap-2019-q3 removed
Note: See TracTickets for help on using tickets.