Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
Onionoo
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • 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.

  • The Tor Project
  • Metrics
  • Onionoo
  • Issues
  • #24495

Closed
Open
Opened Dec 02, 2017 by Iain Learmonth@irl

Add aggregated summary documents

This would be incredibly useful for legacy/trac#23782 (moved). These could also be a form of summary document to give basic stats about the number of relays/bridges having a particular value for a property. An example would be:

https://onionoo.torproject.org/aggregated_summary?group=version

{"version":"4.4",
"next_major_version_scheduled":"2017-12-17",
"build_revision":"25021a8",
"relays_published":"2017-12-02 14:00:00",
"aggregated_relays":{
"0.3.1.8": 30,
"0.3.1.9": 34,
"0.4.5.8": 2
},
"bridges_published":"2017-12-02 13:05:07",
"aggregated_bridges":{
"0.3.1.8": 31,
"0.3.1.9": 24,
"0.4.5.8": 2
}
}

(not real data)

You could use this to produce autocompletion lists for the advanced search form, but it would also have a secondary use for generating bar charts.

It should be easy enough to have the group argument be for any Onionoo details field.

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: tpo/metrics/onionoo#24495