Tracking efforts related to work on the update orphaning dashboard. Given all the efforts going on with the updater, it's worth at least taking a bit of time to try to keep this dashboard up to date.

:chutten - I'm trying to better understand what needs to be changed here in order to keep this dashboard up to date. Other than the obvious "Up to date: the client's Firefox version is 71 or higher on the release channel." text that's now wrong, do you have any more insight into where this dashboard is clearly in need of maintenance?

I see that I can toggle report week in the top righthand corner and it looks like it's updating the dashboard.... so I'm assuming it's pulling in accurate data....but want to confirm this.

I'm flagging you here based on the March 10th slack thread in #firefox since you seem to have some more background here. If that's not the case, and you're not the right person to ask here, let me know :)

I'm not sure what the current status of the job at https://github.com/mozilla/mozilla-reports/blob/master/projects/app_update_out_of_date.kp/orig_src/app_update_out_of_date.ipynb is. Last commit was November 25.

:mreid, do you know anything about what data job might be running the orphaning thingy?

The notebook-based code is no longer in use - Arkadiusz migrated it over to run via DataProc[1], working with :rstrong IIRC.

Arkadiusz, can you comment on the state of the data here? What might be needed to bring the 71 value (and anything else) up to date?

[1] https://github.com/mozilla/telemetry-airflow/blob/master/jobs/update_orphaning_dashboard_etl.py

(In reply to Mark Reid [:mreid] from comment #3)

The notebook-based code is no longer in use - Arkadiusz migrated it over to run via DataProc[1], working with :rstrong IIRC.

That's right, I sent a PR to remove the old version. It seems that :rstrong is no longer at Mozilla, which might be a slight inconvenience here.

Arkadiusz, can you comment on the state of the data here? What might be needed to bring the 71 value (and anything else) up to date?

I think we'd need to:

• change minimum version in the ETL code
• update text on the report page

(In reply to Arkadiusz Komarzewski [:akomar] from comment #4)

I think we'd need to:

• change minimum version in the ETL code
• update text on the report page

Thanks, Arkadiusz - those links are really helpful.

In terms of changing the minimum version in the ETL code, I'm curious why that needs to change? It's hardcoded to 42 right now but that looks to be due to the fact that we only explicitly handle telemetry data in the chart after FF42 and not due to some other limitation. Maybe I'm wrong though?

Ie, I'm wondering if the minumum_version value was put in place not as a limit in terms of how far we can go back in time, but more due to how far we wanted to/were able to go back in time in terms of special casing around update related telemetry errors.

FF42 is the first desktop release post-Telemetry-unification. Going further back than that will give... inconsistent results.

I'm going to take this and at least get the text/relevant details on the report page updated.

As for long term maintenance, I'm not sure that we'll continue to actively maintain this, however since it's at the moment our best source of update stats, I don't want to let it get too far out of date until we have a reasonable replacement. Since this dashboard was built before we started using BigQuery, it's possible that we can build out something similar using re:dash. I'm not sure that's worth the effort if we can get this to "just work", but noting that we may go that route.

For those interested in following update telemetry efforts, I've created a meta update telemetry issue where all related work will be linked.

(In reply to Rachel Tublitz [:rachel] from comment #5)

(In reply to Arkadiusz Komarzewski [:akomar] from comment #4)

I think we'd need to:

• change minimum version in the ETL code
  (...)

In terms of changing the minimum version in the ETL code, I'm curious why that needs to change? It's hardcoded to 42 right now (...)

Good point, I take that back. Changing this would limit the range of versions we capture on the dashboard.

Opened a PR here to get this updated.

PR is merged, closing. If people have feature requests/issues/etc related to this dashboard in the future, just let us know over in the install/update matrix channel.