telemetry-analysis-service
telemetry-analysis-service copied to clipboard
mozilla
Telemetry Analysis Service
The majority of scheduled Spark jobs run an old version of EMR and need to be updated. I think this should include at first doing a one-time notification of their...
`NoSuchKey`: An error occurred (NoSuchKey) when calling the GetObject operation: The specified key does not exist. I believe this is because the output gets saved to the private S3 path...
From https://bugzilla.mozilla.org/show_bug.cgi?id=1370312: I have a notebook which refuses to upload as a gist. Most of them work fine, but not this one. The symptom is when I click the "save...
From https://bugzilla.mozilla.org/show_bug.cgi?id=1365625: The plotly that comes by default on ATMO clusters is ancient. Please update it to plotly 2.0.8 or something equivalently-recent.
From https://bugzilla.mozilla.org/show_bug.cgi?id=1365735: Related to bug 1365625. Using plotly in local mode on a cluster leads to the following error appearing when trying to save a workbook: Notebook Validation failed: ......
This is to be able to more easily associate logs with a specific run
This is about the user experience of providing the date when scheduling new Spark jobs. Right now when scheduling a new Spark job the "start date" and "end date" form...
Users really really should see the "what's new" section as soon as possible. Maybe even move the link to the top bar.
daily-export-of-previous-day-oom-crash-data-v1-to-s3 has been failing every day. The failure email was not sent on 2017-03-31.
Currently we show the status of a cluster as "WAITING" when it is ready for use. This is a bit odd.
