Services still reporting to the old Papertrail account
Categories
(Taskcluster :: General, task)
Tracking
(Not tracked)
People
(Reporter: armenzg, Unassigned)
Details
Attachments
(1 file)
|
17.90 KB,
image/png
|
coop
:
data-review+
|
Details |
Non-Treeherder apps
Services still reporting:
https://papertrailapp.com/systems/releng-tc-coalesce
https://papertrailapp.com/systems/2878091432
https://papertrailapp.com/systems/taskcluster-tools
https://papertrailapp.com/systems/stateless_dns-1
https://papertrailapp.com/systems/taskcluster-events
https://papertrailapp.com/systems/taskcluster-aws-provisioner2
https://papertrailapp.com/systems/cloud-mirror
|
||
Comment 1•5 years ago
|
||
I deleted a bunch of the systems I knew about.
I'd like to leave this one in place if it's OK with you. It's a service that's very difficult to redeploy but that we can't kill very soon, unfortunately. And it doesn't run in Heroku, so we can't use a Heroku add-on for it.
I also see taskcluster-tools -- I'm not sure how to turn that off, but we probably should. Hassan, can you check if there's a setting for that in Heroku? I don't have access anymore.
|
Reporter | |
Comment 2•5 years ago
|
||
It's fine to leave what cannot be easily moved. I appreciate the house cleaning!
|
||
Comment 3•5 years ago
|
||
There doesn't seem to be a papertrail addon in the taskcluster-tools heroku app. Weird...
|
|
||
Comment 4•5 years ago
|
||
It's a log drain, which isn't visible in the UI.
dustin@lamport ~ $ heroku drains -a taskcluster-tools
=== Drains
syslog+tls://logs6.papertrailapp.com:26354 (d.975ea0b0-9cab-4855-94bd-329e3d9e8ea4)
dustin@lamport ~ $ heroku drains:remove -a taskcluster-tools d.975ea0b0-9cab-4855-94bd-329e3d9e8ea4
Successfully removed drain syslog+tls://logs6.papertrailapp.com:26354
|
|
Reporter | |
Comment 5•5 years ago
|
||
Thanks for the clean up!
What do you know about i-0197706ac7ca23e2e..usw2.mozilla.com?
It is in the group called group-awaiting-deletion?
|
|
||
Comment 6•5 years ago
|
||
I peeked at that -- it seems to be a Windows system. I have no idea :)
|
||
Comment 7•5 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #6)
I peeked at that -- it seems to be a Windows system. I have no idea :)
Possibly a generic-worker test instance? cc-ing pmoore just in case.
|
|
||
Comment 8•5 years ago
|
||
Armen: are there still TC services reporting here?
|
|
Reporter | |
Comment 9•5 years ago
|
||
There's still these. Not sure if some belong to releng.
|
|
Reporter | |
Comment 10•5 years ago
|
||
The ones that look like IPs don't have anything useful.
The last two have logs up to today.
|
|
||
Comment 11•5 years ago
|
||
I think relops shut down the tc-coalesce service /cc fubar
stateless-dns is still running, so we should figure out how to log that elsewhere (or not at all..)
|
|
Reporter | |
Comment 12•5 years ago
|
||
Any objections if I remove the IP-like services?
|
|
||
Comment 13•5 years ago
|
||
34.213.136.122 and 52.49.228.53 are also stateless DNS hosts running in different AWS regions, so let's not remove them quite yet until we figure out what to do with them per comment #11.
For the other two IPs, can you find out when they last reported, and maybe even discern what they're logging about from the output?
|
|
||
Comment 14•5 years ago
|
||
|
|
||
Comment 15•5 years ago
|
||
(In reply to Chris Cooper [:coop] pronoun: he from comment #13)
For the other two IPs, can you find out when they last reported, and maybe even discern what they're logging about from the output?
I don't have admin access in this papertrail any more, but looking through the purge events menu, I can tell those two other IPs (185.202.1.161 and 5.188.86.98) are part of the Treeherder custom group.
|
|
||
Comment 16•5 years ago
|
||
(In reply to Armen [:armenzg] from comment #12)
Any objections if I remove the IP-like services?
OK, I've circled completely around back to "Yes, just remove all the IP-based services." They're not logging anything anyway. Sorry for the churn.
|
|
Reporter | |
Comment 17•5 years ago
|
||
I've changed the Treeherder group not to accept messages from new senders (that will exclude some of those static IP systems; even though they were not emitting).
I can't remove those static IP systems.
fubar or coop: Could you please remove them? I see you both have full privileges
https://papertrailapp.com/systems/5442785752/edit
https://papertrailapp.com/systems/5442793302/edit
https://papertrailapp.com/systems/5184777802/edit
https://papertrailapp.com/systems/5187210812/edit
|
|
||
Comment 18•5 years ago
|
||
(In reply to Armen [:armenzg] from comment #17)
fubar or coop: Could you please remove them? I see you both have full privileges
https://papertrailapp.com/systems/5442785752/edit
https://papertrailapp.com/systems/5442793302/edit
https://papertrailapp.com/systems/5184777802/edit
https://papertrailapp.com/systems/5187210812/edit
Oh look , I do have admin privs. Their interface is just terrible. :/
I've removed those systems after verifying that the individual stateless DNS hosts are being aggregated under the single, remaining stateless_dns system. Just need :fubar to verify the status of the coalesce service.
|
|
Reporter | |
Comment 20•5 years ago
|
||
Great!
fubar, coop: could you please remove it? https://papertrailapp.com/systems/releng-tc-coalesce/edit
That would only leave us with the Treeherder app and the stateless-dns services.
|
|
||
Comment 21•5 years ago
|
||
(In reply to Armen [:armenzg] from comment #20)
fubar, coop: could you please remove it? https://papertrailapp.com/systems/releng-tc-coalesce/edit
Done.
|
|
Reporter | |
Comment 22•5 years ago
|
||
Thank you coop!
From my perspective this can be closed unless you want to track doing something with stateless-dns.
|
|
||
Updated•5 years ago
|
Description
•