Closed Bug 1345217 Opened 3 years ago Closed 3 years ago

[Churn] Separate csv uploads to s3 from churn job

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: amiyaguchi, Assigned: amiyaguchi)

Details

Attachments

(2 files)

The Churn notebook generates both parquet and csv data formats for consumption. However, csv will soon lose relevancy once data is consumed from telemetry-parquet.

Separating the logic between generating the data and creating csv files for consumption will make it easier to kill csv as a file format in the future. This also makes the dependencies more clear.
Assignee: nobody → amiyaguchi
Priority: -- → P1
:mreid, can you confirm that the two locations specified in the churn notebook are currently being used?

* net-mozaws-prod-us-west-2-pipeline-analysis/mreid/churn/
* net-mozaws-prod-metrics-data/telemetry-churn/
Flags: needinfo?(mreid)
(In reply to Anthony Miyaguchi [:amiyaguchi] from comment #1)
> :mreid, can you confirm that the two locations specified in the churn
> notebook are currently being used?
> 
> * net-mozaws-prod-us-west-2-pipeline-analysis/mreid/churn/
Yes, this is the location from which data is fetched to be imported into Tableau.

> * net-mozaws-prod-metrics-data/telemetry-churn/
This is the location that automagically relays to the metrics.services.mozilla.com server. I don't think anything is using this data. Matt, can you confirm that nothing is hooked up to that dataset via metrics.s.m.c?
Flags: needinfo?(mreid) → needinfo?(mpressman)
Yep, I an confirm that there is not anything using net-mozaws-prod-metrics-data/telemetry-churn/
Flags: needinfo?(mpressman)
Pull request for mozilla/telemetry-airflow.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.