Closed
Bug 1534790
Opened 6 years ago
Closed 6 years ago
Deactivate and archive taskcluster-stats-collector
Categories
(Taskcluster :: Operations and Service Requests, task)
Taskcluster
Operations and Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Assigned: dustin)
References
Details
Once we stop sending data to statsum, we can shutdown the heroku app (taskcluster-stats-collector) and archive the corresponding github repo (https://github.com/taskcluster/taskcluster-stats-collector)
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → dustin
Assignee | ||
Comment 2•6 years ago
|
||
Its TC client had
auth:aws-s3:read-write:taskcluster-raw-docs/taskcluster-stats-collector/
auth:sentry:tc-stats-collector
auth:statsum:tc-stats-collector
I also deleted its pulse users. Its signalfx token appears to be disabled.
I deleted the testing secrets from the secrets service.
It's not in DNS so there's no difficulty in deleting the Heroku app, which I did.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•