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)
Data Platform and Tools
Documentation and Knowledge Repo (RTMO)
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
Updated•8 years ago
|
Points: --- → 2
Priority: -- → P2
Assignee | ||
Comment 1•8 years ago
|
||
Chris HC has added some relevant analysis recently:
http://reports.telemetry.mozilla.org/post/projects/ping_delays.kp
http://reports.telemetry.mozilla.org/post/projects/crash_ping_delays.kp
Updated•8 years ago
|
Component: Metrics: Pipeline → Documentation and Knowledge Repo (RTMO)
Product: Cloud Services → Data Platform and Tools
Comment 2•8 years ago
|
||
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)
Comment 3•8 years ago
|
||
How much of this was covered by similar topics in https://github.com/mozilla/firefox-data-docs/blob/master/concepts/analysis_gotchas.md
Assignee | ||
Comment 4•8 years ago
|
||
I don't think I'll get to this in Q2, bumping priority accordingly. Thanks.
Flags: needinfo?(mreid)
Priority: P2 → P3
Assignee | ||
Comment 5•8 years ago
|
||
(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
Assignee | ||
Comment 6•7 years ago
|
||
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.
Description
•