1098048 - ship-it errors should be available to releng

Status: RESOLVED DUPLICATE of bug 1134182

(Release Engineering :: Applications: Shipit, defect)

Description

[Nick Thomas [:nthomas] (UTC+12)]

... so we can see errors without having to pester webops. Either we send them to sentry/errormill, or we ask for access to the dev/staging/production servers and get db access too. It's on the generic cluster so that might be harder to arrange.

Comment 1

[[e-mail] (:bhearsum)]

I know Rail and I have access to the generic cluster. I think sentry/errormill would be wonderful to have for this, though - I think it's worked out pretty well for Balrog.

Comment 2

[Lonnen :lonnen]

Hooking it into sentry is mostly self service. Do either of you have accounts with the ability to add new projects to RelEng?

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

I can't see any UI to add a project on my account.

Comment 4

[[e-mail] (:bhearsum)]

I don't think I have access to. I don't see any buttons on https://errormill.mozilla.org/account/teams/Releng/projects/ to add a new project, or anywhere else the UI. I may be blind though.

Comment 5

[Lonnen :lonnen]

Attachment: Screen Shot 2014-11-17 at 3.23.30 PM.png

I'm an admin and your views probably differ from mine. I have a 'create a new project' button in the upper right hand corner, just below my log in. Screenshot attached.


I was talking with Callek in #webdev and for this sort of error reporting: some teams rely on Sentry but most use newrelic. Sentry is minimally supported. If you have cycles I can help set you up to do more than the security patches I apply currently. If you have few errors and a tiny audience, Sentry may be right for you. Otherwise, newrelic is probably good enough.

Comment 6

[[e-mail] (:bhearsum)]

Mass component change for ship it bugs.

Comment 7

[[e-mail] (:bhearsum)]

I suspect New Relic will fulfill our needs.