1637974 - Implement "printed" usage criterion in clients_daily and clients_last_seen

Status: RESOLVED WONTFIX

(Data Platform and Tools :: General, enhancement, P3)

Description

[Jeff Klukas [:klukas] (UTC-4)]

There is a workstream interested in measuring user engagement with various features in desktop Firefox that fits in well with the concept of "usage criteria" in the clients_last_seen methodology as discussed in the Profile Features Work doc. We would like to start tracking more of these activities as bit patterns.

To demonstrate our ability to implement new usage criteria, we want to pursue a concrete case where we can take an existing probe in main pings and plumb that all the way through the ETL chain to clients_last_seen so that we can make MAU-like measurements on it.

We've identified printing as the concrete case to implement. There is an existing print_count probe in main pings. Completing this bug involves:

• Modifying the main_summary query to hit this probe and add a print_count field to the table
• Modify the clients_daily query to sum print_count per client as a new print_count_sum field
• Modify the clients_last_seen query to maintain a days_printed_bits field that records each day that the given client had print_count_sum > 0

This scope of work does not involve backfilling the tables. We would simply add the fields so that new days start having these fields populated.

Note that adding fields to these tables may cause queries to fail if the jobs in telemetry-airflow are not configured to allow schema addition. In particular, the clients_last_seen case may require manually adding the field to the schema since the query references clients_last_seen itself. Feel free to tap :klukas for guidance when we get to that step.

Comment 1

[Rob Miller [:rmiller]]

Hello,

The Mozilla Data Engineering organization is currently going through our extensive backlog, consisting of hundreds of issues stretching back for nearly 10 years. We've done a pass through all of the open bugzilla bugs and have identified and tagged the ones that we think are relevant enough to still need attention. The rest, including the bug with which this comment is associated, we are closing as "WONTFIX" in a single bulk operation.

If you feel we have closed this (or any) issue in error, please feel free to take the following actions:

• Reopen the bug.
• Edit the bug to add the string [dataplatform] (including the brackets) to the Whiteboard field. (Note that you must edit the Whiteboard, not the similarly named QA Whiteboard.)

Doing this will ensure that we see the bug in our weekly triage process, where we will decide how to proceed.

Thank you.

Comment 2

[Rob Miller [:rmiller]]

Hello,

The Mozilla Data Engineering organization is currently going through our extensive backlog, consisting of hundreds of issues stretching back for nearly 10 years. We've done a pass through all of the open bugzilla bugs and have identified and tagged the ones that we think are relevant enough to still need attention. The rest, including the bug with which this comment is associated, we are closing as "WONTFIX" in a single bulk operation.

If you feel we have closed this (or any) issue in error, please feel free to take the following actions:

• Reopen the bug.
• Edit the bug to add the string [dataplatform] (including the brackets) to the Whiteboard field. (Note that you must edit the Whiteboard, not the similarly named QA Whiteboard.)

Doing this will ensure that we see the bug in our weekly triage process, where we will decide how to proceed.

Thank you.