Closed Bug 1534667 Opened 6 years ago Closed 6 years ago

Remove statsum, sentry support from aws-provisioner, ec2-manager

Categories

(Taskcluster :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

No description provided.
Blocks: 1534670
Summary: Remove statsum, signalfx support from aws-provisioner, ec2-manager → Remove statsum, sentry support from aws-provisioner, ec2-manager
Blocks: 1529461
No longer blocks: 1534670

aws-provisioner uses tc-lib-monitor@5.4.0, the code for which is here
https://github.com/taskcluster/taskcluster-lib-monitor/tree/ed33b91b154da51212f5bf1f992c6215408c1bad/src

We want to not pass taskcluster credentials to the constructor (since it will just use them to try to call the auth service). To allow that, we also need to pass enable:false. aws-provisioner doesn't use any logging support in tc-lib-monitor, so that's only going to disable error reporting and metrics. Metrics looks like it will work fine. And if disabled, error reporting logs to console. So I think we're in good shape.

Ec2-manager seems to have a mishmash of tc-lib-* versions that results in its tests trying to access api/ec2-manager/v1/ping, but the service not serving on that path. I'm not sure how that happened (I thought its tests were in better shape).

https://github.com/taskcluster/ec2-manager/pull/78

provisioner-staging works fine

& production

ec2-manager-staging says

2019-03-12T22:47:35.293815+00:00 app[web.1]: { AssertionError [ERR_ASSERTION]: Must provide a rootUrl to taskcluster-lib-monitor

so I pushed a fix to add that back and landed it. All set!

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.