Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #28871

Closed (moved)
(moved)
Open
Created Dec 17, 2018 by Karsten Loesing@karsten

Relay with 6 weeks downtime only has 6_months and 5_years bandwidth graphs

Looks like we didn't consider this rather unusual case:

https://onionoo.torproject.org/bandwidth?lookup=87B3557F3E792217E2BC4E9923EACA4AEC5BA9C3

version	"7.0"
build_revision	"7dc8dae"
relays_published	"2018-12-17 07:00:00"
relays	
0	
fingerprint	"87B3557F3E792217E2BC4E9923EACA4AEC5BA9C3"
write_history	
6_months	
first	"2018-12-14 12:00:00"
last	"2018-12-16 12:00:00"
interval	86400
factor	72.42059244429615
count	3
values	[…]
5_years	
first	"2015-04-20 00:00:00"
last	"2016-02-04 00:00:00"
interval	864000
factor	326.8920611644816
count	30
values	[…]
read_history	{…}
bridges_published	"2018-12-17 06:53:55"
bridges	[]

The effect is that there's no "1 Month" graph (which is unrelated to this issue), a "6 Months" graph with just 3 dots, no "1 Year" graph, and then again a "5 Years" graph with 30 dots.

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