Closed Bug 1145215 Opened 10 years ago Closed 9 years ago

taskcluster-tools: Add mozilla-taskcluster to status.taskcluster.net

Categories

(Taskcluster :: UI, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: pmoore, Unassigned)

References

Details

and potentially to tools.taskcluster.net too if we will have any web view on this service...
Status.taskcluster.net is strictly static... We should add it to tools.tc.net under something like /metrics/status I imagine we can add multiple dashboards under /metrics/
So status.taskcluster.net uses https://uptimerobot.com/ to measure uptime of the webprocess. mozilla-taskcluster doesn't have a web process. I'm open to using another kind of measure. What I like about uptimerobot is that it's not ours, so we can't break it :) (also it's simple and free). For the most part taskcluster can be considered up, when our web processes are up, as this means API requests are received. But I'm very much open to another way of measuring uptime. Maybe we need to use a heroku addon for it. @pmoore, any suggestions? I CC'ed jlal, as he mentioned he wanted mozilla-taskcluster on status.taskcluster.net.
Depends on: 1145212
Flags: needinfo?(pmoore)
Summary: Add mozilla-taskcluster to status.taskcluster.net → taskcluster-tools: Add mozilla-taskcluster to status.taskcluster.net
I'll defer to James, as I'm not sure how we can monitor the uptime.
Flags: needinfo?(pmoore)
We can probably do with something that access heroku APIs. They have metrics... Perhaps we can just find a heroku add-on for showing a status page or something. Granted it would have to cover a collection of apps and not just one.
Component: TaskCluster → General
Product: Testing → Taskcluster
Component: General → Tools
I don't want to... also mozilla-taskcluster is going away slowly.. -- This bug is closed as part of the Great Bugzilla Cleaning Sprint of 2016 by bstack and jonasfj, please reopen if you disagree.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Component: Tools → UI and Tools
You need to log in before you can comment on or make changes to this bug.