Partition executive stream by channel

RESOLVED FIXED

Status

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Importance:
P1
normal
Status:
RESOLVED FIXED
Reported:
3 years ago
Modified:
4 months ago

People

(Reporter: kparlante, Assigned: trink)

Tracking

Firefox Tracking Flags

(Not tracked)

Details
(Reporter)

Description

•
3 years ago 
During the roadmap discussion we mentioned partitioning the executive stream, by channel or other dimensions.
(Reporter)

Comment 1

•
3 years ago 
trink will queue up the work, may not deploy until whd is back
Assignee: nobody → mtrinkala
Priority: -- → P1
 (Assignee)

Updated

•
3 years ago
Flags: needinfo?(whd)
Flags: needinfo?(mreid)

Comment 3

•
3 years ago 
Looks good. Specific comments over in the PR.
Flags: needinfo?(mreid)

Comment 4

•
3 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

•
3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED

Comment 5

•
3 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

•
4 months ago
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.