Closed
Bug 1182693
Opened 10 years ago
Closed 10 years ago
[meta] budget risk mitigation
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kparlante, Assigned: mreid)
References
Details
(Whiteboard: [rC] [unifiedTelemetry])
Updated•10 years ago
|
Assignee: nobody → mreid
Priority: -- → P2
Whiteboard: [rC] [unifiedTelemetry]
Updated•10 years ago
|
Iteration: --- → 43.1 - Aug 24
| Assignee | ||
Comment 1•10 years ago
|
||
Budget factors are being monitored, and will alert (daily) if we exceed our expected incoming volume.
Dashboard is at https://metrics.services.mozilla.com/telemetry-budget-dashboard/
Code to generate that data (and to alert):
https://github.com/mozilla-services/data-pipeline/tree/master/reports/budget
If / when we start to exceed our planned budget, mitigating strategies include:
- Reduce data retention period for "landfill" data
- Reduce data retention period for raw data
- Consider retaining a sample of release data instead of all of it.
| Assignee | ||
Comment 2•10 years ago
|
||
Katie, is there any other action for this bug, or should I close it out?
Flags: needinfo?(kparlante)
| Reporter | ||
Comment 3•10 years ago
|
||
Lets close it out & open new bugs for any cost reduction tasks we take on.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(kparlante)
Resolution: --- → FIXED
Updated•7 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
•