1351402 - Validate the update ping data for the Nightly channel

Status: RESOLVED FIXED

(Toolkit :: Telemetry, enhancement, P1)

Description

[Alessio Placitelli [:Dexter]]

Once bug the "upgrade" ping lands we should make sure to validate the incoming data on our servers. We should at least check:

- That the upgrade ping is received within a reasonable time after an update happens
- That the upgrade information is consistent with the performed update (previous version , current version)

Comment 1

[Alessio Placitelli [:Dexter]]

Attachment: Update ping validation on Nightly

Comment 2

[Alessio Placitelli [:Dexter]]

The analysis was reviewed by Chris and merged [1]. It will be available on RTMO soon.

Summary:

- the majority (99.71%) of the update ping payload data on Nightly looks ok;
- a few pings (< 1%) are reporting a mismatching update channel (due to the CCK tool [2]) or a target update build id older than the current one; the second part can be attributed to the usual Nightly weirdness;
- 93.419% of the clients that sent the update ping updated to the newer Nightly build within a week;
- 79.678% of the clients that were seen on the newer Nightly build sent an update ping: this "low" percentage could be due to automatic updates being disabled, pave-over installs or undocumented/unknown edge cases.

[1] - https://github.com/mozilla/mozilla-reports/blob/master/projects/update_ping_ready_nightly_validation.kp/knowledge.md
[2] - https://mike.kaply.com/cck2/