Telemetry/Custom dashboards with re:dash: Difference between revisions
(→Longitudinal Data: Moving reference link to the front of the intro) |
(Adding main_summary stub) |
||
| Line 10: | Line 10: | ||
{{longitudinal data intro}} | {{longitudinal data intro}} | ||
===Main Summary=== | |||
This is a stub. Ping Ryan Harter (:harter) for current status. | |||
===Google Sheets=== | ===Google Sheets=== | ||
Revision as of 15:55, 8 August 2016
Introduction
Re:dash allows you to connect to various data sources via an interactive SQL frontend. You can then share your queries with peers, create visualizations, or combine these into an automatically updating dashboard.
Check it out at [sql.telemetry.mozilla.org]. re:dash is also known as stmo, an abbreviation of it's URL.
Available Data Sets
Longitudinal Data
See Telemetry/LongitudinalExamples for a discussion of the data and example queries.
The longitudinal dataset is a summary of main pings. If you're not sure which dataset to use for your query, this is probably what you want. It differs from the main_summary table in two important ways:
- The longitudinal dataset groups all data for a client-id in the same row. This makes it easy to report profile level metrics. Without this deduping, metrics would be weighted by the number of submissions instead of by clients.
- The dataset uses a 1% of all recent profiles, which will reduce query computation time and save resources. The sample of clients will be stable over time.
Accordingly, one should prefer using the Longitudinal dataset except in the rare case where a 100% sample is strictly necessary.
As discussed in the Longitudinal Data Set Example Notebook:
The longitudinal dataset is logically organized as a table where rows represent profiles and columns the various metrics (e.g. startup time). Each field of the table contains a list of values, one per Telemetry submission received for that profile. [...]
The current version of the longitudinal dataset has been build with all main pings received from 1% of profiles across all channels with [...] up to 180 days of data.
Main Summary
This is a stub. Ping Ryan Harter (:harter) for current status.
Google Sheets
To access a Google Sheet from re:dash:
- Share the spreadsheet with "gspread@pipeline-sql-prod.iam.gserviceaccount.com".
- Google will warn you that this address is not within Mozilla. Click "OK"
- Find the document ID for the given spreadsheet.
- For example, a URL like "https://docs.google.com/spreadsheets/d/1-DaBLABLAmu_lVGunk8I/edit#gid=1507574279" has an id of "1-DaBLABLAmu_lVGunk8I"
- Paste this id into the query box in sql.telemetry.mozilla.org. As an example, see https://sql.telemetry.mozilla.org/queries/476/source
- You should see your spreadsheet data appear in re:dash
Thanks to Mark Reid and Blake Imsland for sharing!