1298887 - Validate that child telemetry still works after bug 1218576

Status: RESOLVED FIXED

(Toolkit :: Telemetry, defect, P3)

Description

[Chris H-C :chutten]

After bug 1218576 lands, we need to make sure nothing's gone stupid.

Some examples:

1) Keep an eye out for telemetry-alerts. It'll take three days to get there, but I expect absolutely everything would explode if we got aggregator stuff wrong.

2) After one day, check telemetry.mozilla.org. Check parent-only and child-only metrics to make sure they're similar to what came before (subject to the changes as documented on the mailing list (the aggregate measures might be different for child-reported measures because the meaning of "count" changes))

3) After a couple of days, run the E10sExperimentView against nightly. Make sure the result can be run meaningfully through the e10s_experiment.ipynb

4) After one day, run a notebook and check that get_pings from the affected build dates returns full and meaningful results. Verify that get_pings crossing the gap (before and after the build with the change) returns meaningful results as well.

Comment 1

[Georg Fritzsche [:gfritzsche]]

I think we should also check the main ping payloads after the landings verifying that:
* histograms & keyedHistograms moved
* the new processes/content section has the expected keys & correctly typed content etc.

Comment 2

[Chris H-C :chutten]

> 4) After one day, run a notebook and check that get_pings from the affected build dates returns full and meaningful results. Verify that get_pings crossing the gap (before and after the build with the change) returns meaningful results as well.

get_pings reports pings from builds before and after the build with correct numbers (I checked my own clientId). This criteria's a pass.

>* histograms & keyedHistograms moved
>* the new processes/content section has the expected keys & correctly typed content etc.
Raw ping documents look good to me. I consider these passed as well.

Not going to check tmo until tomorrow morning's aggregator run.

Comment 3

[Chris H-C :chutten]

> 2) After one day, check telemetry.mozilla.org. Check parent-only and child-only metrics to make sure they're similar to what came before (subject to the changes as documented on the mailing list (the aggregate measures might be different for child-reported measures because the meaning of "count" changes))

Looking pretty solid, actually: https://mzl.la/2dnq1FH

Comment 4

[Chris H-C :chutten]

Everything checks out!