Closed Bug 742496 Opened 8 years ago Closed 5 years ago
Telemetry data retention policy
Telemetry does not currently have a data retention policy. I would like to discuss the requirements and develop a policy so that it is clear to users how long Telemetry data will be retained. (Note that I consider indefinitely to be a valid request so long as it comes with justification.) To assist in our decision we should identify: 1. any physical constraints (I'm thinking disk space). Daniel - Can you please try to determine how much disk space is currently required to store the Telemetry data from a single day? 2. usage patterns for the data to determine over what time period data is useful. We should also consider whether having different policies for the different channels is warranted as well.
Marking: in group of > 33 asks for Telemetry that need PM priority before triage/scheduling.
Status: NEW → ASSIGNED
Whiteboard: [Telemetry] → Telemetry -- needs PM project priority
Target Milestone: Unreviewed → Backlogged - BZ
> 1. any physical constraints (I'm thinking disk space). > Daniel - Can you please try to determine how much disk space is currently > required to store the Telemetry data from a single day? > At current data size (per record): 192 GB (= 64GB (compressed) x 3 copies (for Hadoop replication)) per day Please note that the data size per record has doubled from ~17k in Q1 to ~35k (now) --
Target Milestone: Backlogged - BZ → Targeted - JIRA
Whiteboard: Telemetry -- needs PM project priority → [Telemetry:P1]
Do you still want this information? I'm not sure if you've already set a lifecycle for how long we keep telemetry data.
bsmedberg - You own Telemetry now. Do you already have a policy for data retention? Is there a need to keep this bug open?
Flags: needinfo?(lmandel) → needinfo?(benjamin)
This is now folded into the Firefox data retention policy in general, along with FHR. Officially we're allowed to do 13-month retention, but we currently plan on storing 180 days.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.