Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #13084
Closed (moved) (moved)
Open
Created Sep 08, 2014 by Roger Dingledine@arma

globe gets read/written backwards in its bandwidth graphs

https://atlas.torproject.org/#details/7552CA84FB125059DC2959A6BE01A6A8107B3523 shows a big jump in bandwidth, especially read bytes.

whereas https://globe.torproject.org/#/relay/7552CA84FB125059DC2959A6BE01A6A8107B3523 shows a big jump in bandwidth, but especially written bytes.

Examination of the extrainfo descriptor for the relay in question shows that it's read-history, not write-history, that has the big numbers.

So I think globe has its labels mixed up?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking