Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #20403

Closed (moved)
Open
Opened Oct 19, 2016 by teor@teor

Make it easier for relay operators to find their observed bandwidth

Hi tom, thanks for #20372 (moved), makes a big difference to relay operators.

I was answering another relay operator question today, and realised I needed the observed bandwidth. Because they were measured high, but then limited by the observed bandwidth.

Is that the sort of thing we can put on consensus health? Under the fingerprint? (Because it's set by the relay, not an authority.) Or another row? Also, should we show the consensus weight?

Or is that just too confusing, and I should direct them to use Atlas, and hover over the bandwidth heading? (If it works, which it doesn't on high security tor browser.)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#20403