[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #22346 [Metrics/Metrics website]: tor browser update URL change and the update ping metrics
#22346: tor browser update URL change and the update ping metrics
-------------------------------------+------------------------------
Reporter: cypherpunks | Owner: metrics-team
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Metrics/Metrics website | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------+------------------------------
Comment (by karsten):
Replying to [comment:6 boklm]:
> Replying to [comment:4 karsten]:
> > boklm, gk, any ideas what we're missing?
>
> I don't see what is missing, or if something is missing.
>
> Would it be possible to run the same request, for the days January 24,
25, 26 (when the update pings dropped), and April 4, 5, 6 (when they
increased), to try to understand what changed? Maybe seeing which type of
URL dropped or increased on those days can tell us if we are missing
something.
Sure, here's the output:
{{{
webstats=> SELECT log_date, site,
webstats-> substr(resource_string, 1,
webstats(> strpos(resource_string, 'update_') + 8) AS resource_part,
webstats-> SUM(count) AS count
webstats-> FROM files NATURAL JOIN requests NATURAL JOIN resources
webstats-> WHERE resource_string LIKE '%/torbrowser/update\__/%'
webstats-> AND resource_string NOT LIKE '%.xml'
webstats-> AND response_code = 200
webstats-> AND method = 'GET'
webstats-> AND (log_date = '2017-01-24'
webstats(> OR log_date = '2017-01-25'
webstats(> OR log_date = '2017-01-26'
webstats(> OR log_date = '2017-04-04'
webstats(> OR log_date = '2017-04-05'
webstats(> OR log_date = '2017-04-06')
webstats-> GROUP BY log_date, site, resource_part
webstats-> ORDER BY log_date, count DESC;
log_date | site | resource_part
| count
------------+------------------------+-------------------------------------------+---------
2017-01-24 | dist.torproject.org | /torbrowser/update_2/
| 2025386
2017-01-24 | aus1.torproject.org | /torbrowser/update_2/
| 33549
2017-01-24 | archive.torproject.org | /tor-package-
archive/torbrowser/update_2/ | 1
2017-01-25 | dist.torproject.org | /torbrowser/update_2/
| 692113
2017-01-25 | aus1.torproject.org | /torbrowser/update_2/
| 151832
2017-01-26 | aus1.torproject.org | /torbrowser/update_2/
| 381621
2017-01-26 | dist.torproject.org | /torbrowser/update_2/
| 362971
2017-01-26 | archive.torproject.org | /tor-package-
archive/torbrowser/update_2/ | 2
2017-04-04 | aus1.torproject.org | /torbrowser/update_2/
| 655434
2017-04-04 | dist.torproject.org | /torbrowser/update_2/
| 50278
2017-04-04 | archive.torproject.org | /tor-package-
archive/torbrowser/update_2/ | 8
2017-04-05 | aus1.torproject.org | /torbrowser/update_2/
| 1488508
2017-04-05 | dist.torproject.org | /torbrowser/update_2/
| 51111
2017-04-05 | archive.torproject.org | /tor-package-
archive/torbrowser/update_2/ | 23
2017-04-06 | aus1.torproject.org | /torbrowser/update_2/
| 1847522
2017-04-06 | dist.torproject.org | /torbrowser/update_2/
| 50576
2017-04-06 | archive.torproject.org | /tor-package-
archive/torbrowser/update_2/ | 11
(17 rows)
}}}
Would you want to play with the database yourself? It's ~3G uncompressed,
so it shouldn't be that hard to dump and compress it. You'd have to
create a local PostgreSQL database and import that file, and then you
could run requests like this yourself. (I'd still be around to help with
the schema as needed!)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22346#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs