Closed Bug 1301820 Opened 8 years ago Closed 7 years ago

Create writeup explaining telemetry date/times, delays, etc.

Categories

(Data Platform and Tools :: Documentation and Knowledge Repo (RTMO), defect, P3)

defect
Points:
2

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kparlante, Assigned: mreid)

References

Details

Cover: - submission date vs user reported activity date - fields associated with above - what we know about clock skew (may require analysis prep) - what we know about submission lag (may require analysis prep) - current mau/dau strategy: https://bugzilla.mozilla.org/show_bug.cgi?id=1240849 - any guidelines for analysis Plan is to have this for the telemetry info meeting ~9/22
Blocks: 1301689
Points: --- → 2
Priority: -- → P2
Component: Metrics: Pipeline → Documentation and Knowledge Repo (RTMO)
Product: Cloud Services → Data Platform and Tools
Hey Mark - does it look like you'll be able to handle this in Q2 or should we move this to P3?
Flags: needinfo?(mreid)
I don't think I'll get to this in Q2, bumping priority accordingly. Thanks.
Flags: needinfo?(mreid)
Priority: P2 → P3
(In reply to Chris H-C :chutten from comment #3) > How much of this was covered by similar topics in > https://github.com/mozilla/firefox-data-docs/blob/master/concepts/ > analysis_gotchas.md There's definitely some overlap with information in there, in particular I think it fully covers these items: - fields associated with [submission date vs user reported activity date] - any guidelines for analysis It also partially covers what we know about submission lag. We also have some ongoing monitoring of submission latency by document type via the CEP[1]. I'd still like to see the distribution of clock skew. [1] For example, for 'main' pings: https://pipeline-cep.prod.mozaws.net/dashboard_output/graphs/analysis.moz_telemetry_doctype_monitor_main.latency.html
I'm calling this done per :chutten's investigations.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.