Closed Bug 1453724 Opened 7 years ago Closed 7 years ago

sentry should include node versions

Categories

(Taskcluster :: Services, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

Details

process.versions has a bunch of useful versions. Those should get included in the error report. It looks like that could be added to `modules` via dataCallback. https://github.com/getsentry/raven-node/issues/449 too
Newer versions of raven do. We're on a very ancient version.
tc-lib-monitor was already updated to a newer version, but it is not widely disseminated. I've also landed bug 1452000 in tc-lib-monitor, so I'll upgrade to get both, in some less-than-critical services like hooks. https://github.com/taskcluster/taskcluster-hooks/pull/92
That's a rather random assortment of the pushes I made.. Anyway, taskcluster-stats-collector needs some additional TLC here, as it was running a *very* old version of tc-lib-monitor and upgrading causes the tests to fail. Other than that, this is complete.
We're going to leave tc-stats-collector as-is. The major issue seems to be that the updated version of tc-lib-monitor prefixes the project name onto the metric name, so tasks.<workerType>.running becomes tc-stats-collector.tasks.<workerType>.running. I don't really know if that's a problem. The service is not part of a redeployable cluster, and may not even be useful for Firefox anymore, so for now I'll just leave it at the ancient version of the library.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Platform Libraries → Services
You need to log in before you can comment on or make changes to this bug.