Open Bug 1244741 Opened 8 years ago Updated 2 years ago

Limit the precision of the creationDate field.

Categories

(Toolkit :: Telemetry, defect, P4)

defect

Tracking

()

Tracking Status
firefox47 --- affected

People

(Reporter: Dexter, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [measurement:client])

The dates in the main-ping are limited to a daily precision, but the creationDate (which is part of the common ping format) isn't.

We should probably limit this one as well so that it has a daily precision.
Blocks: 1201022
Priority: -- → P3
Whiteboard: [measurement:client]
I don't think we should limit it to daily precision, but use a precision of seconds, minutes or hours.

Currently we submit the full hhmmss.sss, i think we don't need the fractional part at all.
I think a precision of minutes is enough for all questions we might want to answer from this, which would be related to distributions of ping creation times.

Benjamin, does that sounds ok from your data collection review perspective?
Flags: needinfo?(benjamin)
creationDate being the date/time this ping was created, or the profile creation date/time?

I don't understand the tradeoffs here: who uses this piece of data? Do we use this to determine operational latency, for example? If so, having something smaller than days is probably useful.

I don't think I have enough context about why this field exists to answer the question at hand.
Flags: needinfo?(benjamin)
Priority: P3 → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.