Closed
Bug 1218259
Opened 9 years ago
Closed 8 years ago
Persist first_seen_at across node re-assignments
Categories
(Cloud Services Graveyard :: Server: Token, defect)
Cloud Services Graveyard
Server: Token
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rfkelly, Unassigned)
Details
In Bug 1173407 we added a "first_seen_at" property to tokenserver user records, for the purpose of tracking user-retention behaviour. Unfortunately it was a bit of a hack-job and it doesn't persist across node-reassignments - if we reassign a user's node, they appear to be a completely new user. It seems to have been useful so let's do the work of tracking it properly so that it persists across node-reassignments.
Reporter | ||
Comment 1•8 years ago
|
||
I suspect we won't need to persist this explicitly given the new redshift-based metrics stuff :dcoates is working on; ni? Danny to close if it doesn't sound valuable going forward.
Flags: needinfo?(dcoates)
Comment 2•8 years ago
|
||
I agree. With the (hashed) fxa uid flowing through to the token and storage servers we'll have all the info we need.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(dcoates)
Resolution: --- → WONTFIX
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•