Closed
Bug 1617710
(fxa-metrics-migration)
Opened 5 years ago
Closed 3 years ago
[Meta] Migration of FxA metrics to the Data Platform
Categories
(Data Platform and Tools :: General, enhancement, P3)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: klukas, Assigned: klukas)
References
Details
Overall tracking bug for data pipeline-side work to support the migration of FxA metrics off of custom infrastructure.
Updated•5 years ago
|
Points: --- → 5
Priority: -- → P3
Comment 1•5 years ago
|
||
Note: I set this to P3 as has been our usual practice for [Meta] bugs - this work is high priority, which will be reflected in the actionable sub-bugs.
Assignee | ||
Updated•5 years ago
|
Alias: fxa-metrics-migration
Assignee | ||
Comment 2•5 years ago
|
||
Note that metrics work from the FxA is paused until H2, so we won't make any more progress on the streaming Amplitude pipeline for the time being.
I'll be focusing on ETL tasks here for the rest of H2. In particular, we'll prioritize based on whether there are any pieces of infrastructure we can deprecate (FxA heka pipeline, FxA Redshift) by having replacement data source provided via scheduled queries.
Assignee | ||
Comment 3•3 years ago
|
||
I'm not aware of any further work that will be happening in this stream.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•