(In reply to Chris Cooper [:coop] pronoun: he from comment #1) > Related: there are a handful of non-Taskcluster people (mostly releng and CIDuty) who also have access to SignalFX. I'll be emailing them to make sure they have nothing of value still in SignalFX. I've reached out to everyone who had an account in SignalFX, and o one uses SignalFX but us (TC). I've started deleting accounts and removing alerts/detectors. There were two active access tokens that I just disabled: 1) statsum-kubernetes, created by bstack on Apr 8, 2018 2) tc-stats-collector-tests, create by dustin on Jul 15, 2018 Brian: the statsum-kubernetes token was received ~2,000/min. The source will likely start failing now that token is disabled. Should we turn this off at the source? Does that involve shutting down statsum (bug 1529461 and bug 1534672)?
Bug 1534841 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Chris Cooper [:coop] pronoun: he from comment #1) > Related: there are a handful of non-Taskcluster people (mostly releng and CIDuty) who also have access to SignalFX. I'll be emailing them to make sure they have nothing of value still in SignalFX. I've reached out to everyone who had an account in SignalFX, and o one uses SignalFX but us (TC). I've started deleting accounts and removing alerts/detectors. There were two active access tokens that I just disabled: 1) statsum-kubernetes, created by bstack on Apr 8, 2018 2) tc-stats-collector-tests, create by dustin on Jul 15, 2018 Brian: the statsum-kubernetes token was receiving ~2,000/min when I disabled it. The source will likely start failing now that token is disabled. Should we turn this off at the source? Does that involve shutting down statsum (bug 1529461 and bug 1534672)?