Closed
Bug 1300847
Opened 8 years ago
Closed 7 years ago
Add TxP experiment installation info into main_summary
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: isegall, Unassigned)
References
Details
We'd like to get the mau/dau statistics from main_summary for txp experiments as it's a battle-tested source of truth and easy to query (also, this is the model we'll be using in the future for rolling experiments out through addons). We'd like to add a field for "active txp addon" (right now, we're getting these from addon names in the main ping, which is laborious). Essentially, we need to know that:
-user x
-was on firefox on day d
-has experiment e installed
for all users in txp.
Updated•8 years ago
|
Updated•8 years ago
|
Points: --- → 2
Priority: -- → P2
Comment 1•8 years ago
|
||
Ilana, can you link to an example notebook that pulls the txp addon info out of the main ping?
Flags: needinfo?(isegall)
Flags: needinfo?(isegall)
Comment 3•7 years ago
|
||
This should be solved by including all addon info in the main_summary dataset. Please reopen if this is still needed.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•