Closed
Bug 1208235
Opened 10 years ago
Closed 10 years ago
Partition executive stream by channel
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kparlante, Assigned: trink)
Details
During the roadmap discussion we mentioned partitioning the executive stream, by channel or other dimensions.
| Reporter | ||
Comment 1•10 years ago
|
||
trink will queue up the work, may not deploy until whd is back
Assignee: nobody → mtrinkala
Priority: -- → P1
| Assignee | ||
Comment 2•10 years ago
|
||
| Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(whd)
Flags: needinfo?(mreid)
Comment 4•10 years ago
|
||
Looks good here too. I think we should deploy this sooner rather than later so that we can backfill the data, unless we are expecting more changes to the executive stream. I'll speak to :relud about getting it deployed.
| Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 5•10 years ago
|
||
This was deployed on 10/27.
aws s3 ls s3://net-mozaws-prod-us-west-2-pipeline-data/telemetry-executive-summary-3/20151030/
PRE Other/
PRE aurora/
PRE beta/
PRE nightly/
PRE release/
Flags: needinfo?(whd)
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
•