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
  • #24218

Closed (moved)
Open
Opened Nov 10, 2017 by Karsten Loesing@karsten

Implement new metrics-web module for IPv6 relay statistics

The sample graphs I made for #23761 (moved) are based on some quick-and-dirty Java code that we need to rewrite in a more robust and more scalable way before putting these graphs on Tor Metrics.

Here's my plan for implementing this module, and I'm curious to hear possible alternatives or improvements:

  • We start with a design quite similar to the recently added webstats module. This basically means creating:

    • a PostgreSQL database schema for import tables and aggregations/views and
    • a Java class to import into the database and run queries.
  • I believe that the data aggregation won't scale to years of data. My hope is that we can solve this in the database by using some triggers to only include newly added data in the aggregation.

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