average-response
average-response copied to clipboard
amtunlimited
REST API for aggregates.telemetry.mozilla.org
As requested in https://github.com/amtunlimited/average-response/blob/71a4e9653d13f888f5158fc1d8226dc37c8bee3e/script.js#L32 you can find the API's documentation here: https://github.com/mozilla/python_mozaggregator/#api
Alternatively you could use the telemetry.js script itself, documented over thisaway: https://github.com/mozilla/telemetry-dashboard/blob/gh-pages/v2/doc.md
As for https://github.com/amtunlimited/average-response/blob/71a4e9653d13f888f5158fc1d8226dc37c8bee3e/script.js#L20 the histogram encoding format is surprisingly not (yet?) documented anywhere but code (it wasn't considered an API surface, really, so that's probably an oversight). That last "0" is for overflow and is vestigial because we're encoding categorical data in a continuous numerical histogram. It's a bad hack from years ago, but a useful one.
Oh, and Hi! I'm chutten. I'm in charge of telemetry.mozilla.org's Measurement Dashboards and the Firefox Telemetry system in Firefox Desktop. Feel free to find me or my team mates on #telemetry:mozilla.org if you have any questions. I love your page: it's excellent.
(( Some interesting context: Your average might not be for The Web At Large since our Nightly population is a little on the weird side, being primarily devs and other nerds. You can see this from the max concurrent tab count metrics: nightly's interpolated median is 3.19 and beta's is 2.06. Generally speaking "normal" subsessions have very few tabs, and neither Nightly nor Beta will give you a properly full sample of The Web At Large. (Our Beta channel is also a little on the weird side, and we don't publish release data at the moment) ))
(( Hm. I wonder if the average response code is different between the two populations... and if it changes over time... ))