Opened 4 weeks ago

Closed 2 weeks ago

Last modified 2 weeks ago

#31755 closed task (fixed)

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

Reported by: boklm Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Website Version:
Severity: Normal Keywords:
Cc: tbb-team, metrics-team Actual Points:
Parent ID: Points:
Reviewer: irl Sponsor:

Description

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.

Child Tickets

Attachments (2)

webstats-tb-channel.png (123.7 KB) - added by karsten 2 weeks ago.
webstats-tb-channel.2.png (132.2 KB) - added by karsten 2 weeks ago.

Download all attachments as: .zip

Change History (10)

Changed 2 weeks ago by karsten

Attachment: webstats-tb-channel.png added

comment:1 Changed 2 weeks ago by karsten

I made a very quick graph:


Does this very roughly match your expectation? I'll cross-check this result by myself, and irl is going to review the code once it's available. But did you expect the numbers to look roughly like this or very different from this?

comment:2 Changed 2 weeks ago by boklm

Thanks!

Yes, I expect the alpha numbers to be very small compared to the stable ones. Would it be possible to have separate graphs for alpha and stable, with a different scale, so that we can better see the alpha numbers?

Changed 2 weeks ago by karsten

Attachment: webstats-tb-channel.2.png added

comment:3 Changed 2 weeks ago by karsten


How's this? (Note that I only changed the visualization but did not further check the numbers behind it.)

comment:4 Changed 2 weeks ago by boklm

This looks good, thanks!

I think the numbers are plausible. It's interesting to see that the two graphs are almost the same (except for the scale).

comment:5 Changed 2 weeks ago by karsten

Cc: metrics-team added
Reviewer: irl
Status: newneeds_review

Great! Thanks for checking the attached graph for plausibility. I also took another look at the code and didn't find anything obviously wrong. I'll assume the numbers are good unless otherwise told.

irl, please review commit cba1711 in my task-31755 branch.

comment:6 Changed 2 weeks ago by irl

Status: needs_reviewmerge_ready

Still no closer to working out why the pings sometimes double/halve, but looks good to me.

comment:7 Changed 2 weeks ago by karsten

Resolution: fixed
Status: merge_readyclosed

Thanks! Merged and deployed. Enjoy! Closing.

comment:8 in reply to:  6 Changed 2 weeks ago by boklm

Replying to irl:

Still no closer to working out why the pings sometimes double/halve, but looks good to me.

Ah, we'll be able to see if they double/halve at the same time for the stable/alpha.

Note: See TracTickets for help on using tickets.