1791000 - Implement a custom ping in FOG to emulate a possible nodc implementation

Status: RESOLVED FIXED

(Toolkit :: Telemetry, task)

Description

[Perry McManis [:perry.mcmanis]]

There's a super cool proposal for adding a Nightly only Data Capture Ping

See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1784314

This is for a small experiment to evaluate what value the proposed ping might bring, before any application or SDK changes are made.

Note: this is not an A/B or A/A experiment; this is small scale proof of concept.

It will be implemented by making a custom ping in FOG, setting the schedule analagously to what the final ping's schedule would look like, and manually adding a few metrics. We will then compare specifically how does data in this ping look in the first 3 days compared to the same measures collected in the metrics ping

Acceptance Criteria: capture at least as much of the distribution of the same measures from the legacy main ping (represented by the proportion of total pings collected and the number of clients represented), with a 10% margin on the levels from the main ping (to allow for some small slack inherent from comparing two different data collection systems)

Comment 1

[Chris H-C :chutten]

A note on impact risk: Creating a ping that isn't sent in all configurations might result in the Glean SDK storing data that is never sent (and thus never cleared). This may add cruft to the database.

For this trial I recommend either (or both):

1. Reading through the storage layer to familiarize yourself with what happens to data that is recorded to pings that are not sent and are then removed. (Document your findings in the Glean Dev Book)
2. Landing the ping and unlanding the ping within the same Nightly cycle, thereby ensuring that the only affected population is the same population that was sending the ping. (IOW: don't let the ping escape Nightly)

Comment 2

[Chris H-C :chutten]

(Data Steward Hat On) Given that this will add a collection of existing data from the same population, the existing data reviews for the individual metrics should apply for them.

Comment 3

[Perry McManis [:perry.mcmanis]]

Attachment: Bug 1791000 - Implement a custom ping in FOG to emulate a possible nodc implementation r?chutten

Comment 4

[Perry McManis [:perry.mcmanis]]

Attachment: Bug 1791000 - Implement a custom ping in FOG to emulate a possible nodc implementation r?chutten

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/c4f2f3f71ae6
Implement a custom ping in FOG to emulate a possible nodc implementation r=chutten

Comment 6

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/c4f2f3f71ae6