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

Closed (moved)
(moved)
Open
Created 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
Time tracking