Closed Bug 1286273 Opened 8 years ago Closed 8 years ago

Improve s.t.m.o. documentation

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rvitillo, Assigned: harter)

References

Details

User Story

We should refactor and improve the little documentation we have about Re:dash (and Presto) on our wiki, similarly to what we did in the past for our probes [1]. A new employee should be able to read the documentation and have all he needs to run simple analyses and/or build dashboards.

[1] https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Adding_a_new_Telemetry_probe

References:
- https://robertovitillo.com/2016/03/27/telemetry-meets-sql/
- https://wiki.mozilla.org/Telemetry/LongitudinalExamples
- http://www.slideshare.net/RobertoAgostinoVitil/growing-a-sql-query
No description provided.
Blocks: 1286269
Assignee: nobody → rharter
User Story: (updated)
User Story: (updated)
Priority: -- → P2
I added a new wiki page to serve as a repo for all re:dash/stmo documenation: https://wiki.mozilla.org/Custom_dashboards_with_re:dash I also added a bunch of tips/tricks I stumbled upon while working on bug 1286262 to: https://wiki.mozilla.org/Telemetry/LongitudinalExamples
Status: NEW → ASSIGNED
The longitudinal set cannot be sampled using the sample_id as previously instructed in the examples. Fixed this section. https://wiki.mozilla.org/index.php?title=Telemetry%2FLongitudinalExamples&diff=1142373&oldid=1141913
Depends on: 1286277
re:dash/stmo documentation is complete. There's not much to document - re:dash is pretty straightforward, all the datasets are available on the available datasets wiki page, and all the difficulties of dealing with longitudinal have already been documented in LongitudinalExamples. Seems we can call this complete. One thing to consider is adding more Data Sources.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.