Closed
Bug 1632605
Opened 5 years ago
Closed 4 years ago
Create update orphan tracking dashboard in BigQuery - split out by channel
Categories
(Toolkit :: Application Update, task, P1)
Toolkit
Application Update
Tracking
()
RESOLVED
FIXED
People
(Reporter: rachel, Assigned: rachel)
References
()
Details
It looks like we can access update error data now via BiqQuery in ways that we could not previously when the update orphaning dash was created.
To start, let's make a simple dash that shows: The distribution of up to date/out of date (concern)/out of date (possible concern) over time, split out by channels.
Assuming that's do-able, I'll file follow ups to add for specific errors.
Logic by channel will be as follows:
- Release - up to date = major versions going back 2 behind release.
- Beta & Dev Edition - up to date = major versions matching release.
- Nightly - up to date = running a current weekly release.
Assignee | ||
Updated•5 years ago
|
Priority: P2 → P1
Assignee | ||
Comment 1•5 years ago
•
|
||
WIP, dash lives here
This includes release only for now, working on adding the other channels next. Once those are added, I'll make these a bit easier to read, ie convert to %.
Assignee | ||
Updated•4 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•4 years ago
|
||
Add Nightly and resolved issues with the release query.
Final dashboard is https://sql.telemetry.mozilla.org/dashboard/update-orphans-over-time.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•4 years ago
|
Summary: Create update error tracking dashboard in BigQuery - split out by channel → Create update orphan tracking dashboard in BigQuery - split out by channel
You need to log in
before you can comment on or make changes to this bug.
Description
•