1386609 - Volume of new profile pings is smaller than new profiles in main pings in beta

Status: RESOLVED FIXED

(Toolkit :: Telemetry, defect, P1)

Description

[Anthony Miyaguchi [:amiyaguchi]]

This bug was reported in the #fx-metrics channel.[1] The count of new profiles over a week of beta in `telemetry_new_profile_parquet` is smaller than the count of new profiles in `main_summary`. 

The volume of the new profile ping should correspond to number of unique profiles in main_summary that contain subsession_start and profile_creation dates in the same week. The count used for reproducing this issue is applied to the week of 2017-07-18.[1] However, porting the query from longitudinal to main_summary shows that the new profile ping volume is lower than expected.[2]

This query assumes that new profiles in beta collected in the week of 2017-07-18 are installing using builds that enable the new profile ping by default.

[1] https://mozilla.slack.com/archives/C4D5ZA91B/p1501603174331219
[2] https://sql.telemetry.mozilla.org/queries/10526/source
[3] https://sql.telemetry.mozilla.org/queries/10552/source

Comment 1

[Anthony Miyaguchi [:amiyaguchi]]

The queries should filter down on the app_build_id, using '20160612' as the start date. 

> WHERE substr(app_build_id, 1, 8) > '20160612'

The new profile ping volume under these constraints [1] is significantly larger than the main_summary equivalent [2].

[1] https://sql.telemetry.mozilla.org/queries/11127/source
[2] https://sql.telemetry.mozilla.org/queries/11100/source

Comment 2

[Alessio Placitelli [:Dexter]]

The magic number for the build id filtering comes from when Firefox 55 hit the Beta channel, which is 12th June 2017.

[1] - https://wiki.mozilla.org/RapidRelease/Calendar