Closed Bug 1355712 Opened 7 years ago Closed 7 years ago

Validate (sub)sessionStartDate changes

Categories

(Toolkit :: Telemetry, enhancement, P1)

Product:
Toolkit
Component:
Telemetry
Type:
enhancement
Points:
1

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox55 --- affected

People

(Reporter: gfritzsche, Assigned: bugzilla)

References

(Blocks 1 open bug)

Details

(Whiteboard: [measurement:client]) 

In bug 1349324, we changed sessionStartDate and subsessionStartDate to hourly precision.
We need to validate that the incoming data reflects that and looks sane.
Sunah, can you pick this up?
Flags: needinfo?(ssuh)
Priority: -- → P2
Whiteboard: [measurement:client]
Assignee: nobody → ssuh
Flags: needinfo?(ssuh)
Points: --- → 1
Priority: P2 → P1
Here are my findings:
https://gist.github.com/sunahsuh/e4c27018a28df4514e55dad037fb3415
(Note I ignored timezone entirely in the aggregation)

At first I was concerned about the jump in subsessionStartDate at midnight but then I realized it's expected due to subsession split on the day boundary.

Let me know if you think there's anything else I should do to validate, but it looks like we're getting the right thing.
Flags: needinfo?(gfritzsche)
This makes sense. We don't have any noise in the data, yay.

Raw numbers numbers are hard to read though, a visual for the value distribution would have made this much faster to review.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(gfritzsche)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.