Closed
Bug 1145212
Opened 9 years ago
Closed 7 years ago
taskcluster-tools: Add status.taskcluster.net to tools.taskcluster.net
Categories
(Taskcluster :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Unassigned)
References
Details
No description provided.
Comment 1•9 years ago
|
||
Great idea... Let's put it under: tools.taskcluster.net/metrics/status I think we're going to build a large collection of dashboards built on stats from influxdb. So tools.taskcluster.net/metrics probably has to be a meta page with an overview of what dashboards we do have :)
Summary: Add status.taskcluster.net to tools.taskcluster.net → taskcluster-tools: Add status.taskcluster.net to tools.taskcluster.net
Reporter | ||
Updated•9 years ago
|
Component: TaskCluster → General
Product: Testing → Taskcluster
Comment 2•9 years ago
|
||
We can harvest some info from heroku too.. Note: this feed should probably also include information about deployments. Ideally auto-generated, so we can always see what code rolled out.
Reporter | ||
Comment 3•9 years ago
|
||
Worker Type updates might also be interesting for sheriffs - is that something to put here, or have a separate feed for that? Primarily, existing worker types that get an updated ami are probably of most relevance, as this is essentially like a new deployment of a taskcluster component, and could be a reason for bustage that would interest sheriffs. New worker types are probably not as significant.
Comment 4•9 years ago
|
||
workerTypes should probably be documented by the provisioner. I guess this could be part of the discussion to add description as well.
Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•