1504879 - [Adhoc] Telemetry Probe EDA and Behavior Repo / Reporting

Status: RESOLVED INACTIVE

(Data Science :: General, task)

Description

[Su-Young Hong]

Brief description of the request:

Figure out process for reporting, storing, and keeping EDA for individual probes (for example, the bookmarks probes bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1402134) 
- how can we keep findings about individual probes and their behavior and wierdness in one place? 
- what should the process be? 
- do it a few times 

https://docs.google.com/document/d/1vcC5Uy_rGSRxo636fekUqtFwef6hNpnH93pIa8t3-tA/edit#

Link to any assets:

Is there a specific data scientist you would like or someone who has helped to triage this request:

reported by shong assigned to shong by shong

Comment 1

[Su-Young Hong]

Bug Plan

Summary: I want to create some official location where analysis, descriptions, and documentation of Telemetry probe EDA can officially "live". That way:

• When team members are doing EDA on probe behavior as part of their regular workflow, they have a place to put that work without altering their workflow too much.
• We have a central place we can point users who have questions about how certain probes work

DTMO isn't a very good candidate because that supports markdowns, and a lot of these reports will be sort of quick notebooks.

Potential candidates:

• a Github repo under the Mozilla/ org ("telemetry-eda"?)
• a class of reports submitted to r.t.m.o with titles starting "Telemetry EDA"

How I imagine this will work:

• Data scientists will upload their work to the location, with the probe or the metric affected clearly defined
• Link from DTMO to in a probe EDA section to the location
• Individual links in the Probe Dictionary for specific probes that have entries in the location

Comment 2

[Su-Young Hong]

Action Plan:

• 1: I create a repo that will have this work
  • • Include README.md with description of what this repo is
  • • Also include general instructions for what goes in, how to format, etc.
• 2: I seed the repo with my own EDA work
  • • candidate: first use date
  • • candidate: bookmarks probe
  • • candidate: tracking protection probe
  • • GLS candidate: probe
• 3: I publicize and evangelize this within our team
  • • team meeting
  • • ??
• 4: I publicize to Data Platform and Engineering team
  • • reach out to Georg's team for getting integration with probe dictionary
• 5: Publicize generally and try to get broader adoption
  • • ??

Comment 3

[Su-Young Hong]

not sure how much progress I'll get on this and is non-priority.

closing this as inactive. can re-open if I decide to pursue this in the future