Suggestions for the new unified FHR/Telemetry/Experiment ping

[Vladan Djeric]

On Tue, Jan 27, 2015 at 3:18 PM, Brendan Colloran <bcolloran at mozilla.com>
wrote:

> * Vlad, you mention "A single missing or corrupted fragment in a long
> session means we won't be able to recreate the session.


As Georg said in his reply, there were 2 bugs causing missing clientIDs.
Unlike FHR, most Telemetry analyses are done with Nightly data, so
Telemetry is more vulnerable to someone landing a patch that breaks
"stitching" (e.g. breaks clientID reporting) for a few days.


> * If I'm reading you proposal correctly, you're not proposing any
> changes to the data that will be collected by FHR (or telemetry?) or
> any changes to the way FHR data will be binned and aggregated-- you're
> just advocating for a more conservative roll out plan, yes?
>

That's right. Basically I'm suggesting we preserve current Telemetry
semantics in the new unified ping until the session stitching on the
backend is ready and tested. I'm not proposing any alterations to FHR
plans, except possibly a less aggressive schedule for making client-side
changes -- I'm not sure what the timelines are around switching FHR to the
unified ping.

Vladan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/fhr-dev/attachments/20150127/3876c490/attachment.html>