Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

display telemetry-based uptake faster #257

Open
philipp-sumo opened this issue May 1, 2018 · 1 comment
Open

display telemetry-based uptake faster #257

philipp-sumo opened this issue May 1, 2018 · 1 comment

Comments

@philipp-sumo
Copy link

this is a feature request i'd have for the delivery dashboard - it would be great if the telemetry based uptake rate would be updated more often than with a 24h latency.

for example for the current 59.0.3 release which started rolling out yesterday, the dashboard shows:
2018-05-01 19_21_32-start

while over at https://data-missioncontrol.dev.mozaws.net/#/release/windows/main_crashes the usage-hours are updating continuously and show a uptake rate of ~30% of 59.0.3 over 59.0.2 currently:
2018-05-01 19_22_03-start

it would be great if the delivery dashboard could use the same data source too to provide "live" updates about the uptake of a particular release.

@wlach suggested on irc:

we could probably do a periodic redash query which counted the usage hours of recent versions
e.g. maybe something like: https://sql.telemetry.mozilla.org/api/queries/52459/results.json?api_key=QbeyepeMT6174oOO5UbCfkbYJujj84N7eJCrxqzC

@mostlygeek
Copy link
Contributor

mostlygeek commented May 1, 2018

@mreid-moz is it possible to have a faster than 24hr latency? This is the pollbot query that fetches the data. Could we use a lower latency there and get what we need?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants