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

Closed (moved)
Open
Opened Sep 16, 2019 by boklm@boklm

Separate update pings and update requests graphs for Tor Browser alpha and release users

On https://metrics.torproject.org/webstats-tb.html we have some graphs showing the number of Update pings and Update requests from Tor Browser users.

Those numbers currently include both alpha and release users. However it would be nice to be able to know how many alpha users we have. For that we could have separate graphs for alpha and release users.

According to https://metrics.torproject.org/stats.html#webstats-tb the update_pings and update_requests are counted with:

  • update_pings: GET requests to all sites with resource strings '%/torbrowser/update\__/%' and response code 200. To separate alpha and release users we could use the resource strings '%/torbrowser/update\__/alpha/%' and '%/torbrowser/update\__/release/%'.
  • update_requests: GET requests to all sites with resource strings '%/torbrowser/%.mar' and response code 302. Separating update_requests is more difficult as the URL does not include the word alpha or release. However it includes the version number (as the name of the directory under /torbrowser/), which includes an a in case of an alpha version, and no letter (only numbers and dots) in case of a stable release.
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#31755