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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened Sep 14, 2017 by cypherpunks@cypherpunks

Implement family-level pages showing aggregated graphs

Currently atlas is about single relays, many operators run more than a single relay and would like to see the aggregated data of all their relays on a single page with the graphs showing all relays in stacked way. This allows them to see how they are doing across all their relays.

example graphs: https://nos-oignons.net/Services/index.en.html

To avoid discussing how to identify MyFamilies lets just use onionoo lookup: https://atlas.torproject.org/#search/family:

This would also create an incentive for properly configuring MyFamily since incorrect set MyFamily would result

relay operators find this useful (counted ~11) https://lists.torproject.org/pipermail/tor-relays/2017-September/012942.html https://twitter.com/nusenu_/status/907366138149044224

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#23509