Clear metrics with 'lifetime: user' if they expire
Categories
(Data Platform and Tools :: Glean: SDK, task, P1)
Tracking
(Not tracked)
People
(Reporter: Dexter, Assigned: Dexter)
References
Details
Attachments
(2 files)
We currently don't provide any way to clear 'lifetime: user' metrics, even though they expire.
We should fix that so that any expired metric with the user lifetime gets purged from the user profile.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Here's the current set of options we have: https://docs.google.com/document/d/1gWkYRJu2Elk_eQlmbSRHtrZLH-h_2BZ0632OXSRPa0E/edit#
What do you think? Please do leave feedback on the doc!
Updated•5 years ago
|
Comment 2•5 years ago
|
||
It's definitely a complex problem, and I don't have a clear preference for any of the options as I think we will have some difficulties with components/libraries that consume Glean. I see the need to have an API in Glean to register the components' allow-lists/tables and I see this as being a potential source of synchronization issues depending on when components are initialized and can interact with such an API.
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Clearing my needinfo after a first read through the doc.
Assignee | ||
Comment 4•5 years ago
|
||
This problem is effectively an hard nut to crack :-) We discussed this internally and decided on a reasonable strategy for moving forward.
- We will de-emphasize the docs for ‘user’ lifetime, discouraging their use.
- We will create a built-in list of currently known 'user' lifetime metrics in the SDK, to deal with their expiration.
- (optional) we could create the built-in list from probe-scraper, in the future, if we see the number of such metrics grow.
This bug will deal with (1) and (2). Bug 1625123 will handle (3), if needed.
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
•
|
||
We will tackle this bug after the 1st of February, 2021. That's the date when all of the user
lifetime metrics we're aware of will expire (most of them being in m-c).
The decision was due to the following reasons:
- hardcoding the list of know expirations in the code right now doesn't buy us anything compared to waiting;
- any expiration hardcoded in the SDK will work on "run time" date versus the "build time" expiration date we're using for all the metrics;
- we need to disable adding expirations to 'user' lifetimes anyway (see bug 1626516);
We can partially re-use what's in this PR for removing the data from the expired metrics.
Assignee | ||
Updated•5 years ago
|
Comment 8•4 years ago
|
||
Moving this to incoming as a reminder for us to triage it at our next meeting, as decided 10 months ago.
Updated•4 years ago
|
Assignee | ||
Comment 9•4 years ago
|
||
There's two metrics that have expiration in 2022. Metrics with user
lifetime should never expire, so we should fix these up.
Updated•4 years ago
|
Assignee | ||
Comment 10•4 years ago
|
||
Hey,
the GFX team fixed comment 9 :-) Anything else we need to do here?
Comment 11•4 years ago
|
||
With nothing left to expire there's nothing to cleanup. I'm glad we didn't invest time to roll out a code change for this back in the day. :)
Description
•