Closed
Bug 1174930
Opened 9 years ago
Closed 7 years ago
Test that data expires off the server according to policy
Categories
(Data Platform and Tools :: Monitoring & Alerting, defect, P2)
Data Platform and Tools
Monitoring & Alerting
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kparlante, Unassigned)
References
Details
(Whiteboard: [unifiedTelemetry][rC])
No description provided.
Updated•9 years ago
|
Updated•9 years ago
|
Comment 1•9 years ago
|
||
Not needed right away as this is for RC, but can you share links to the policy and how to check data expiry?
Flags: needinfo?(kparlante)
Reporter | ||
Comment 2•9 years ago
|
||
We don't have the complete policy put together yet. This should be pushed out to after 40b9, data validation and other work is taking priority.
Updated•9 years ago
|
Iteration: --- → 43.2 - Sep 7
Updated•7 years ago
|
Iteration: 43.2 - Sep 7 → ---
Component: Metrics: Pipeline → Monitoring & Alerting
Product: Cloud Services → Data Platform and Tools
Comment 3•7 years ago
|
||
:whd, this is using S3 bucket expiration, right? As such, I'm convinced it works as expected.
Can you confirm that expiration is in place for the Telemetry data?
Flags: needinfo?(whd)
Comment 4•7 years ago
|
||
(In reply to Mark Reid [:mreid] from comment #3)
> :whd, this is using S3 bucket expiration, right? As such, I'm convinced it
> works as expected.
>
> Can you confirm that expiration is in place for the Telemetry data?
Expiration is in place for the canonical store and its affect can be empirically verified, bug #1429615 being one such case.
Flags: needinfo?(whd)
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•6 years ago
|
Flags: needinfo?(kparlante)
You need to log in
before you can comment on or make changes to this bug.
Description
•