Closed Bug 1311816 Opened 9 years ago Closed 9 years ago

Make desktop retention data available in re:dash

Categories

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

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cmore, Assigned: amiyaguchi)

References

Details

In bug 1226379, we ported python programs that created retention roll ups from FHR to telemetry. We want to have the same rolls ups available in re:dash for more ad hoc analysis. This will be needed for regular retention reporting and also the desktop attribution project in bug 1259607 and specifically the reporting needs for attribution in bug 1309290. These are the tableau reports that we use now and the fields that are available to tableau, should be the same fields that should be available in re:dash.
Blocks: 1309290
Points: --- → 3
Priority: -- → P2
Assignee: nobody → amiyaguchi
Depends on: 1316336
Depends on: 1321414
Priority: P2 → P1
Depends on: 1324943
Depends on: 1304503
Are there any particular requirements on how far back this dataset should go? The churn dataset is currently available on redash under presto as the table `churn`, between the dates of September 4 - December 4 2016.
No longer depends on: 1304503
Flags: needinfo?(chrismore.bugzilla)
Depends on: 1304503
(In reply to Anthony Miyaguchi [:amiyaguchi] from comment #1) > Are there any particular requirements on how far back this dataset should > go? The churn dataset is currently available on redash under presto as the > table `churn`, between the dates of September 4 - December 4 2016. given the 180 day moving window of telemetry, you probably won't go back any further than that. September 2016 should be fine as how far back to go.
Flags: needinfo?(chrismore.bugzilla)
The churn dataset should now be generated weekly and available to redash. I'll be watching this over the next week or two to make sure that everything is working okay.
Status: NEW → RESOLVED
Closed: 9 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.