Closed Bug 1630705 Opened 5 years ago Closed 5 years ago

Continued updates for update orphaning dashboard.

Categories

(Toolkit :: Application Update, task, P2)

Product:
Toolkit
Component:
Application Update
Type:
task

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: rachel, Assigned: rachel)

References

(
URL
)

Details

Wish list

I'll see how many of these I can roll into one, and then get a PR open.

  1. Add a separate page/tab for looking at trends over time. This should not be default as it's going to load a lot more data than the default page. I'm also going to meet with Arkadiusz before starting this, to make sure we can't get this data instead into re:dash where it won't require custom charting js.

  2. Explore date logic:

I recently updated the dashboard, but am noting an issue:

Assuming this runs every Monday at 2:00 UTC, then we should have gotten 75 back as reportDetails.latestVersion - it looks like we're getting back 74. The page is also requesting this file https://analysis-output.telemetry.mozilla.org/app-update/data/out-of-date/20200412.json...which may be part of the problem. It doesn't look like we have a report for the 13th (or at least the request 404s).

I'd expected this number to jump to 75 this week after running the report on Monday, April 13th since FF75 went live last Tuesday the 7th.

I'm going to guess we need to tweak the ETL logic here vs the front-end of the dash. TBD.

  1. Add link to where FE code lives.
Summary: Fix date on update orphaning dashboard. → Continued updates for update orphaning dashboard.
See Also: → 1621976

Closing this one for the time being as won't fix. It looks like we are now able to do some of this stuff in BigQuery - I'm going to shift efforts over there.

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.