Closed Bug 1255458 Opened 10 years ago Closed 10 years ago

Validate Fennec release "core" ping submissions

Categories

(Toolkit :: Telemetry, defect, P1)

All
Android
defect
Points:
2

Tracking

()

RESOLVED FIXED
Tracking Status
firefox48 --- affected

People

(Reporter: gfritzsche, Assigned: gfritzsche)

References

Details

(Whiteboard: [measurement:client] )

In bug 1247605 we created a notebook to run various checks on incoming Fennec "core" pings. We should use this as a basis to check the "core" ping data on release once we have a few days of release data from Fennec 45.
Priority: P2 → P1
Assignee: nobody → gfritzsche
I'll also re-run the ping volume analysis i did.
This is a re-run of the validation from bug 1247605 with some added details: https://gist.github.com/georgf/c9f4824e5d3bbf112db7 Notable bits: * the count of clients seems surprisingly low (only about ~201,000 as of today) * we have a smaller quality issue with profileDate: * 161 times it is missing * 641 times it is < 10957 (but >= 0) (i.e. a date before the year 2000) * 101 times it is > 17167 (i.e. a date with year 2017+) * Examples of those issues are printed at [54] I'll file bugs on those.
Alessio, can you give this notebook a sanity check?
Flags: needinfo?(alessio.placitelli)
I also re-ran my size analysis and it still holds up on per-client volume. I'd hold back on conclusions though until we have seen a substantial portion of the clients.
(In reply to Georg Fritzsche [:gfritzsche] from comment #2) > This is a re-run of the validation from bug 1247605 with some added details: > https://gist.github.com/georgf/c9f4824e5d3bbf112db7 The notebook looks fine.
Flags: needinfo?(alessio.placitelli)
I'm dropping this for now until we know more about the release population issue.
Assignee: gfritzsche → nobody
We ran this and filed bugs for the problems we are seeing right now. Closing this, future investigations can go into new bugs.
Assignee: nobody → gfritzsche
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.