Closed
Bug 1476407
Opened 7 years ago
Closed 7 years ago
Remove gfx-trends and gfx-telemetry scheduled jobs
Categories
(Data Platform and Tools Graveyard :: Telemetry Analysis Service (ATMO), enhancement)
Data Platform and Tools Graveyard
Telemetry Analysis Service (ATMO)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhunt, Assigned: robotblake)
Details
(Whiteboard: [DataOps])
The gfx-trends and gfx-telemetry scheduled spark jobs on ATMO are used to update the graphics telemetry dashboard [1] [2]. This dashboard was maintained by David Anderson before he left Mozilla.
I'd like to take over updating the analysis scripts, but they're still running somehow on ATMO.
Could someone with admin access deactivate the old jobs so I can upload new versions?
[1] https://github.com/FirefoxGraphics/moz-gfx-telemetry
[2] https://firefoxgraphics.github.io/telemetry/
Comment 1•7 years ago
|
||
Hi Ryan,
It's better to just re-assign the old jobs and let you upload a new notebook via the usual editing interface.
@jason I've changed the "created by" field for gfx-trends successfully via https://analysis.telemetry.mozilla.org/admin/jobs/sparkjob/11/change/.
But wasn't able to do the same for "gfx-telemetry" on https://analysis.telemetry.mozilla.org/admin/jobs/sparkjob/8/change/ where it just responds with a blank 400 error. I don't see anything in the Sentry logs which makes me wonder if this is a CSRF issue or something.
Could you please do the change via the Django management console? Ryan's user id is 250 if that helps.
Flags: needinfo?(jthomas)
Comment 2•7 years ago
|
||
Redirecting to blake.
Flags: needinfo?(jthomas) → needinfo?(bimsland)
Whiteboard: [DataOps]
| Assignee | ||
Comment 3•7 years ago
|
||
Updated the "gfx-telemetry" job via the Django shell to point at :rhunt.
Assignee: nobody → bimsland
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(bimsland)
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•