Closed Bug 1341717 Opened 8 years ago Closed 8 years ago

Write "Common Analysis Gotchas"

Categories

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

defect
Points:
3

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: harter, Assigned: chutten)

References

Details

This document will highlight some common data issues encountered when analyzing telemetry data. For example: * User vs Session weighting * Profiles vs Users * Opt-in vs Opt-out * Dates and their caveats These topics should not be
{hit submit too soon} These topics do not need to be covered extensively. The goal is to make the reader aware of these problems so they know to be cautious when building analyses sensitive to these problems. We should have extensive documentation for these issues either in RTMO or in the "Datasets and Data Collection" section.
Priority: -- → P3
Looking to have this done for Q2.
Assignee: nobody → chutten
Status: NEW → ASSIGNED
Will this cover the date-related topics in Bug 1301820 too?
Flags: needinfo?(chutten)
I wasn't planning on it... but upon reflection, it seems like a good subsection to cover under this broader heading. "Time is Hard, and pings don't make it easy" Could cover the different types of delay, the different date formats. I suppose the perils of having high-resolution client timestamps aren't really _analysis_ gotchas, but maybe I could drive-by the problem.
Flags: needinfo?(chutten)
Priority: P3 → P2
Moving to P2 since we're hoping to have this in Q2.
Component: Metrics: Pipeline → Documentation and Knowledge Repo (RTMO)
Product: Cloud Services → Data Platform and Tools
Priority: P2 → P1
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.