Closed Bug 1309878 Opened 9 years ago Closed 9 years ago

Better documentation for analysis output visibility

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: rvitillo, Unassigned)

References

Details

User Story

In the analysis output visibility field there is no mention of which buckets the description is referring to and users have to ask for help.

We should also document in which prefix they can expect their data to end up and which files are automatically uploaded after the job completes.
No description provided.
I'm not sure how to get to that data, can you elaborate what would be a fitting description?
Flags: needinfo?(rvitillo)
Flags: needinfo?(rvitillo) → needinfo?(mdoglio)
I think :rvitillo is referring to these buckets [1]. The artifacts of a job run (typically a notebook) are uploaded here [2]. The path to the uploaded files is s3://<output-bucket>/<job-name>/data/ [1]https://github.com/mozilla/telemetry-analysis-service/blob/15fcde0b88c361b2abfa1b3fdd2dbf2e403d0f5a/atmo/settings.py#L103-L104 [2]https://github.com/mozilla/emr-bootstrap-spark/blob/456304143b0caf9a09bd7ba53ab7d98f633464c5/ansible/files/batch.sh#L106
Flags: needinfo?(mdoglio)
Points: --- → 1
Priority: -- → P2
Moved to https://github.com/mozilla/telemetry-analysis-service/issues/195
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.