Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • O Onionoo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 45
    • Issues 45
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • Metrics
  • Onionoo
  • Issues
  • #25175
Closed
Open
Issue created Feb 08, 2018 by Karsten Loesing@karsten

Change 3 months graphs to 6 months graphs

As of yesterday (cf. legacy/trac#16513 (moved) and legacy/trac#24729 (moved)), we're retaining bandwidth and weights histories on 24 hour granularity for 6 months rather than just 3. In 3 months from today (May 2018) we can extend the 3 months graphs to 6 months graphs with a granularity of 24 hours per data point.

If we decide to do this, the "3_month" string will change to "6_month", and the object will contain twice as many values. We should make sure that Relay Search can handle this before we make this change.

Requires a minor protocol version change.

Assignee
Assign to
Time tracking