Closed Bug 1335714 Opened 8 years ago Closed 8 years ago

Validate Event Telemetry on Beta

Categories

(Toolkit :: Telemetry, defect, P2)

defect
Points:
2

Tracking

()

RESOLVED FIXED
Tracking Status
firefox54 --- affected

People

(Reporter: gfritzsche, Assigned: bugzilla)

References

Details

(Whiteboard: [measurement:client])

+++ This bug was initially created as a clone of Bug #1302671 +++ We need to validate Event Telemetry from the incoming Beta data, based on bug 1302669. See bug 1302671 for the prior validation on Nightly.
Blocks: 1335715
No longer blocks: 1302662
Assignee: nobody → ssuh
This looks as expected: https://gist.github.com/sunahsuh/74ea3efec9bd3649b072fc14b9997830 Georg, can you take a look over the notebook to make sure I'm not missing anything?
Flags: needinfo?(gfritzsche)
Re "Out[9]": Having a significant number of pings with 'events section is None' on Beta is unexpected. Can we restrict `get_pings()` further with "version" to find out? If that doesn't help we should break this down a bit to see if we can explain this with: - "odd developer builds" or - rare failures client-side (we fall back to `null` in case of failure to serialize the events)
Flags: needinfo?(gfritzsche) → needinfo?(ssuh)
Could we review that better on RTMO? From what i hear its supposed to be much easier for leaving comments.
We could, but from what I can tell you can't leave comments on individual lines on RTMO either. I've updated the gist and after restricting the app version and we no longer have pings without an events section. I'm not sure why the build id restriction wouldn't catch these. Please take another look.
Flags: needinfo?(ssuh)
Thanks, this looks good to me then. I suspect local builds here; devs etc. building locally from older Firefox Beta source. They would have older versions, but the buildid would be based on their current date. If we were concerned we could check whether these are "few" users, but from the volume in the previous gist it seems fine.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.